search for: circunstances

...ayout. >> >> What's the rationale for this? > > Data layout is a property of the target, not the program being > compiled. If you don't like structure packing etc, use packed > structure types. Then, Module::setDataLayout should be removed or make it fail on those circunstances, shouldn't it?

...39;s the rationale for this? >> >> Data layout is a property of the target, not the program being >> compiled. If you don't like structure packing etc, use packed >> structure types. > > Then, Module::setDataLayout should be removed or make it fail on those > circunstances, shouldn't it? I'm not opposed to having it fail when something semantic (like the alignment of double) is wrong. The hints like the 'native integer types' should not cause it to fail. -Chris

In X86Subtarget.h there is a method `getDataLayout' which selects the data layout depending on the platform, ignoring whatever the user setted with Module::setDataLayout. What's the rationale for this?

On Jul 4, 2010, at 6:43 PM, Óscar Fuentes wrote: > In X86Subtarget.h there is a method `getDataLayout' which selects the > data layout depending on the platform, ignoring whatever the user setted > with Module::setDataLayout. > > What's the rationale for this? Data layout is a property of the target, not the program being compiled. If you don't like structure packing

Dear R: First of all, nothing is wrong! I just had a question about the following" "Natural language support but running in an English locale" What does than mean, please? Thanks in Advance R 2.1.0 Windows Laura Holt mailto: lauraholt_983 at hotmail.com

...>>> >>> Data layout is a property of the target, not the program being >>> compiled. If you don't like structure packing etc, use packed >>> structure types. >> >> Then, Module::setDataLayout should be removed or make it fail on those >> circunstances, shouldn't it? > > I'm not opposed to having it fail when something semantic (like the > alignment of double) is wrong. The hints like the 'native integer > types' should not cause it to fail. Then I guess that the information provided by the user through Module::setD...

Buffer overflow detect in FC6-x86_64, see down. Juan. R version 2.4.0 (2006-10-03) Copyright (C) 2006 The R Foundation for Statistical Computing ISBN 3-900051-07-0 R ? um software livre e vem sem GARANTIA ALGUMA. Voc? pode redistribu?-lo sob certas circunst?ncias. Digite 'license()' ou 'licence()' para detalhes de distribui??o. R ? um projeto colaborativo com muitos

You may have noticed I added an "inlinehint" attribute to the IR yesterday, to represent user declarations that hint inlining would be a good idea ("inline" keyword). Chris and I have been discussing how to hook it up to the C++ FE. Consider: class X { int A(int x) {....} inline int B(int x); }; inline int X::B(int x) {...} Per the language standard, A and B

Good afternoon gentlemen (and ladies). A costumer of mine has many servers and each one maps their SIP extensions to the others via DUNDi. It works like a charm. SIP extensions can only register at one server, the one they "belong" to. In case one extension wants to call other that is registered in another server, DUNDi takes care of that by calling the other server using IAX2 and G.729