[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-12 Thread rguenther at suse dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 --- Comment #13 from rguenther at suse dot de 2013-02-12 11:11:11 UTC --- On Tue, 12 Feb 2013, matt at use dot net wrote: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 > > --- Comment #12 from Matt Hargett 2013-02-12 02:02:3

[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-11 Thread matt at use dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 --- Comment #12 from Matt Hargett 2013-02-12 02:02:33 UTC --- looking at the patch for merging elsewhere, I noticed that location_t lto_input_location (struct bitpack_d *bp, struct data_in *data_in) { + static const char *current_f

[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-11 Thread matt at use dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 --- Comment #11 from Matt Hargett 2013-02-12 01:55:28 UTC --- can you add the reduced test case you came up with to the testsuite? I've seen these issues come and go at various points.

[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-08 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-08 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 --- Comment #9 from Richard Biener 2013-02-08 12:55:19 UTC --- Author: rguenth Date: Fri Feb 8 12:55:13 2013 New Revision: 195884 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=195884 Log: 2013-02-08 Richard Biener P

[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-08 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 Richard Biener changed: What|Removed |Added Status|WAITING |ASSIGNED AssignedTo|una

[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-08 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 --- Comment #7 from Richard Biener 2013-02-08 10:10:14 UTC --- Testcase: t.c: volatile int b; int foo (int *); int main () { int a; b = foo (&a); return 0; } t2.c: - int foo (int *a) { return *a; } > g

[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-08 Thread rguenther at suse dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 --- Comment #6 from rguenther at suse dot de 2013-02-08 09:07:09 UTC --- On Thu, 7 Feb 2013, manu at gcc dot gnu.org wrote: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 > > Manuel L?pez-Ib??ez changed: > >Wha

[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-07 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 Manuel López-Ibáñez changed: What|Removed |Added CC||manu at gcc dot gnu.org --- Commen

[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-07 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 --- Comment #4 from Richard Biener 2013-02-07 14:35:24 UTC --- (In reply to comment #3) > (In reply to comment #1) > > Index: gcc/lto-streamer-in.c > > === > > --- gcc/lto-s

[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-07 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 --- Comment #3 from Richard Biener 2013-02-07 14:01:50 UTC --- (In reply to comment #1) > Index: gcc/lto-streamer-in.c > === > --- gcc/lto-streamer-in.c (revision 19584

[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-07 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 --- Comment #2 from Richard Biener 2013-02-07 13:54:20 UTC --- To clarify, we are also switching between different translation-units main filenames - but I don't think we can easily distinguish this from #includes. Well, maybe we can, if a

[Bug middle-end/56231] warning traces have bogus line information when using LTO

2013-02-07 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56231 Richard Biener changed: What|Removed |Added Keywords||lto Status|UNCONFIR