http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32998
philomath changed:
What|Removed |Added
CC||philomath868 at gmail dot
|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32998
--- Comment #15 from Jakub Jelinek 2011-07-22
20:03:35 UTC ---
Author: jakub
Date: Fri Jul 22 20:03:33 2011
New Revision: 176652
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=176652
Log:
PR other/32998
* common.opt (grecord-gcc-s
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32998
--- Comment #14 from Jakub Jelinek 2011-07-12
16:26:10 UTC ---
Created attachment 24746
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24746
gcc47-pr32998.patch
Untested patch to implement a new switch, -grecord-gcc-switches, which records
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32998
--- Comment #13 from Jan Kratochvil
2011-04-22 18:49:06 UTC ---
CU specific -O flag indication is needed for proper prologue skipping:
http://sourceware.org/bugzilla/show_bug.cgi?id=12573
[rfc, 7.3?] -O2 -g breakpoints internal error + prolog
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32998
--- Comment #12 from Roland McGrath 2010-10-05
19:24:56 UTC ---
Preprocessing stuff is probably best left to the -g3 info instead. cc1*
options make sense for DW_AT_producer.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32998
--- Comment #11 from Jakub Jelinek 2010-10-05
09:48:32 UTC ---
I agree, it would be a good idea to append all preprocessing and compilation
options, except for -I/-i* paths (and leave out driver/link options like -B,
-V, -L, -Wl, too), to DW_AT_p
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32998
--- Comment #10 from Roland McGrath 2010-10-05
00:41:45 UTC ---
(In reply to comment #9)
> Wouldn't be appropriate to append these flags also/instead to DW_AT_producer?
> This way they get easily associated with the specific CU.
That makes some
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32998
--- Comment #9 from Jan Kratochvil
2010-10-02 16:06:39 UTC ---
Wouldn't be appropriate to append these flags also/instead to DW_AT_producer?
This way they get easily associated with the specific CU.
--- Comment #8 from manu at gcc dot gnu dot org 2010-06-20 21:20 ---
I think this is pretty much confirmed.
--
manu at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #7 from jsm28 at gcc dot gnu dot org 2010-06-20 21:05 ---
The "-D_GNU_SOURCE a.c" issue is now fixed.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32998
--- Comment #6 from jsm28 at gcc dot gnu dot org 2010-06-20 21:03 ---
Subject: Bug 32998
Author: jsm28
Date: Sun Jun 20 21:02:46 2010
New Revision: 161053
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=161053
Log:
PR other/32998
* opth-gen.awk: Generate definitio
--- Comment #5 from nickc at redhat dot com 2007-08-07 08:25 ---
Subject: Re: -frecord-gcc-switches issues
Hi Ben,
> Is there an easy way to separate out the include and link (-I, -L) bits from
> the macro defines and compiler option flags? Could the just the include bits
> be
> put
--- Comment #4 from nickc at redhat dot com 2007-08-07 08:11 ---
Subject: Re: -frecord-gcc-switches issues
Hi Roland,
> Absolute file names are a very bad idea. That makes for gratuitous
> differences
> in builds due to the build or source directory name, i.e. unrepeatable
> builds
--- Comment #3 from roland at redhat dot com 2007-08-06 19:19 ---
Absolute file names are a very bad idea. That makes for gratuitous differences
in builds due to the build or source directory name, i.e. unrepeatable builds.
The names in .debug_line and .debug_info are already expected
--- Comment #2 from bkoz at gcc dot gnu dot org 2007-08-06 16:16 ---
thanks for adding this bug report here and ccing me.
Is there an easy way to separate out the include and link (-I, -L) bits from
the macro defines and compiler option flags? Could the just the include bits be
put int
--- Comment #1 from nickc at redhat dot com 2007-08-06 08:12 ---
Subject: Re: New: -frecord-gcc-switches issues
Hi Jakub,
> .ascii "-isystem ./include-fixed"
> .zero 1
> .ascii "-D_GNU_SOURCE a.c"
> .zero 1
> The main issue I have with this is t
16 matches
Mail list logo
