search for: flag_merge_const

...constant initialized arrays or initialized constant variables with integral or floating point types. Languages like C or C++ require each non-automatic variable to have distinct location, so using this option will result in non- conforming behavior. In reality, we should handle this by setting flag_merge_constants = 2 in darwin.c, and documenting it. All code that does merging should be testing flag_merge_constants and respecting it. People that don't want merging are then free to turn it off. It is this experience that gives rise to the idea that changing the standard to merge would not...

On Oct 15, 2008, at 7:34 PM, Eli Friedman wrote: > This bug actually manifests itself in two places: one is > ConstantMerge, the other is the AsmPrinter. It's non-trivial to fix > because it's really a design bug: we assume that constant==mergeable, > which simply isn't true. There are a few different ways of fixing > this; however, I think the only real option is to

On Wed, Oct 15, 2008 at 8:28 AM, Chris Lattner <clattner at apple.com> wrote: >> I do think however that it's bit dangerous to combine static constants >> across compilation units. > > GCC does the same things with strings in some cases. You shouldn't > depend on this behavior if you want portable code. Combining is explicitly allowed for strings in C: