Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* GCC 3.4 vs GDB 6.1
@ 2004-01-08 20:30 Andrew Cagney
  2004-01-08 20:33 ` Daniel Jacobowitz
  2004-01-09  8:57 ` Eli Zaretskii
  0 siblings, 2 replies; 7+ messages in thread
From: Andrew Cagney @ 2004-01-08 20:30 UTC (permalink / raw)
  To: gdb

(kind of a bit late but ...)
Are there any "bugs" GDB would like to see fixed in GCC 3.4?

I ask this 'cos GDB starting to really use GCC's DWARF 2 info means (per 
PPC 64) GDB is also identifying occasional problems in GCC's DWARF 2 code.

I'm wondering if there are problems that people know about.

Andrew


^ permalink raw reply	[flat|nested] 7+ messages in thread
* Re: GCC 3.4 vs GDB 6.1
@ 2004-01-08 21:24 Michael Elizabeth Chastain
  0 siblings, 0 replies; 7+ messages in thread
From: Michael Elizabeth Chastain @ 2004-01-08 21:24 UTC (permalink / raw)
  To: cagney, gdb

> (kind of a bit late but ...)
> Are there any "bugs" GDB would like to see fixed in GCC 3.4?

  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12267
  [3.4 regression] function-at-a-time generates stabs in bad order

This imparirs stabs+ support significantly.

Anonymous unions are another regression area.

I have "compare by gcc" tables but I haven't analyzed them yet.
This one bug causes so many problems that it's hard to look at
other stabs+ problems.

Grossly, there are about 27 new FAILS with gcc HEAD -gdwarf-2
versus gcc 3.3.2 -gdwarf-2, and about 28 new FAILS with gcc HEAD
-gstabs+ versus gcc 3.3.2 -gstabs+.

Michael C


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2004-01-10 16:34 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-08 20:30 GCC 3.4 vs GDB 6.1 Andrew Cagney
2004-01-08 20:33 ` Daniel Jacobowitz
2004-01-09  8:57 ` Eli Zaretskii
2004-01-09 14:36   ` Daniel Jacobowitz
2004-01-10 11:54     ` Eli Zaretskii
2004-01-10 16:34       ` Daniel Jacobowitz
2004-01-08 21:24 Michael Elizabeth Chastain

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox