This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/50199] [4.7/4.8 Regression] wrong code with -flto -fno-merge-constants
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 14 Jan 2013 14:55:45 +0000
- Subject: [Bug middle-end/50199] [4.7/4.8 Regression] wrong code with -flto -fno-merge-constants
- Auto-submitted: auto-generated
- References: <bug-50199-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50199
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-01-14 14:55:45 UTC ---
(In reply to comment #14)
> I'm not sure this isn't an issue without LTO
> though (possibly way harder to trigger though).
I don't see how. -fno-merge-constants doesn't say that constants aren't merged
within the same TU, they are merged always, -fno-merge-constants is about not
allowing constants to be merged between different object files. As without LTO
we operate at the level of individual TUs, we don't have issues with that.
-fno-merge-constants is the only possible thing on targets that don't have
needed support on the assembler/linker side though.