This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/51782] -ftree-sra: Missing address-space information leads to wrong
- From: "jamborm at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 21 Feb 2012 13:12:56 +0000
- Subject: [Bug middle-end/51782] -ftree-sra: Missing address-space information leads to wrong
- Auto-submitted: auto-generated
- References: <bug-51782-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51782
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |http://gcc.gnu.org/ml/gcc-p
| |atches/2012-02/msg01080.htm
| |l
--- Comment #27 from Martin Jambor <jamborm at gcc dot gnu.org> 2012-02-21 13:12:56 UTC ---
(In reply to comment #25)
> > Unfortunately, with the patch I got following new LTO link failures on
> > x86_64-linux:
> >
> > gcc.dg/lto/trans-mem-1 c_lto_trans-mem-1_0.o-c_lto_trans-mem-1_1.o link, -flto
> > -fgnu-tm
> > gcc.dg/lto/trans-mem-2 c_lto_trans-mem-2_0.o-c_lto_trans-mem-2_1.o link, -flto
> > -fgnu-tm
> > gcc.dg/lto/trans-mem-4 c_lto_trans-mem-4_0.o-c_lto_trans-mem-4_1.o link, -flto
> > -fgnu-tm
> >
> > I'll have a look a that, even though they look rather scary.
>
> Don't you see the failures without the patch (see pr52297)?
No, I don't, for some reason. Nevertheless, it indeed seems to be an
unrelated problem and so I have posted the patch to the mailing list
and now only wait for test results on a platform with address spaces:
http://gcc.gnu.org/ml/gcc-patches/2012-02/msg01080.html