Re: Designs for better debug info in GCC

2007-12-22 Thread Andrew Haley
Alexandre Oliva writes: > On Dec 21, 2007, Ian Lance Taylor <[EMAIL PROTECTED]> wrote: > > > > Alexandre, I have to say that in my opinion absurd arguments like this > > do not strengthen your position. > > I'm sorry that you feel that way, but I don't understand why you and > so many ot

Re: Designs for better debug info in GCC

2007-12-22 Thread Robert Dewar
Andrew Haley wrote: We know you don't understand, but that isn't likely to change. Would it not surely be better to cease this pointless argument and get on with the job of improving debuginfo? This absolutist position you seem to have adopted isn't helping. If we could talk about "better" an

glibc 2.7 complex functions are possibly miscompiled by gcc 4.3 trunk

2007-12-22 Thread Ismail Dönmez
Hi all, I am doing glibc 4.3 regression tests using gcc 4.3 trunk nearly every day and I see 3 tests fail : math/test-float math/test-ildoubl math/test-ifloat The erorrs are all similar : Failure: Test: Imaginary part of: cacosh (-0 + 0 i) == 0.0 + pi/2 i Result: is: 0.00

Re: Designs for better debug info in GCC

2007-12-22 Thread Ian Lance Taylor
Chris Lattner <[EMAIL PROTECTED]> writes: > If debug info size and link time is really such a serious problem for > so many users, perhaps people developing the gnu toolchain should > investigate an extension like this. I'm in favor of implementing this. As I'm sure you know, the GNU binutils an

Re: Strange error message from gdb

2007-12-22 Thread Jan Kratochvil
On Thu, 20 Dec 2007 15:33:14 +0100, Andrew Haley wrote: > Alexandre Oliva writes: > > > > How about this patch, instead? It will restore debuggability to Java > > while at the same time maintaining the progress of using the > > long-supported-by-GDB DW_TAG_class_type in both C++ and Java. > > >

Re: Designs for better debug info in GCC

2007-12-22 Thread Andi Kleen
Ian Lance Taylor <[EMAIL PROTECTED]> writes: > I'm in favor of implementing this. Yes it would be great. > As I'm sure you know, the GNU > binutils Actually binutils only barely supports debuginfo. AFAIK objcopy is the tool tool that knows anything about them. > and gdb already support usin

Regarding WITH_CLEANUP_EXPR

2007-12-22 Thread Prabhanjan Kambadur
Dear All, This is Anju from IU, Bloomington. I am trying to inject some code into the program and encountered a strange error enroute. Essentially, I am trying to create an std::vector and then call "resize()" on it. "T" is program dependent. When "T" is a primitive type, everything seems to work

Re: Designs for better debug info in GCC

2007-12-22 Thread Daniel Jacobowitz
On Sat, Dec 22, 2007 at 11:49:23PM +0100, Andi Kleen wrote: > > As I'm sure you know, the GNU > > binutils > > Actually binutils only barely supports debuginfo. AFAIK > objcopy is the tool tool that knows anything about them. I don't know why you say that. ld knows a bit about debugging section

Re: Designs for better debug info in GCC

2007-12-22 Thread Andi Kleen
> I don't know why you say that. ld knows a bit about debugging > sections, and how to read .debug_line for errors; objdump knows how to > decode debug info, as does readelf; strip knows how to remove it; > objcopy how to copy and separate it. Sorry I mean separate debuginfo, as Ian was refering

Re: Designs for better debug info in GCC

2007-12-22 Thread Daniel Jacobowitz
On Sun, Dec 23, 2007 at 02:33:44AM +0100, Andi Kleen wrote: > > I don't know why you say that. ld knows a bit about debugging > > sections, and how to read .debug_line for errors; objdump knows how to > > decode debug info, as does readelf; strip knows how to remove it; > > objcopy how to copy and

Re: Designs for better debug info in GCC

2007-12-22 Thread Frank Ch. Eigler
Ian Lance Taylor <[EMAIL PROTECTED]> writes: > [...] Because a compiler that generates incorrect instructions is > completely useless for all users. Surely you overstate this: gcc has always included a generous serving of incorrect-code-generation bugs. > A compiler that generates incorrect de