[Bug debug/54534] [4.7 Regression] Missing location for unused variable

[brobecker at gnat dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54534

Joel Brobecker  changed:

   What|Removed |Added

 CC||brobecker at gnat dot com

--- Comment #2 from Joel Brobecker  2012-09-10 
21:59:26 UTC ---
Hello, here is another example in Ada where we are also missing the location
information even though, at least on the surface, the variable is used:

with Ada.Text_IO; use Ada.Text_IO;

procedure Subprogram is
   X : String := "hello";
   Y : String := "goodbye";
   Z : constant String := X & Y;
begin
   Put_Line (X);  --  BREAK HERE
   Put_Line (Y);
   Put_Line (Z);
end Subprogram;

Trying to print the value of variables X and Y yield the same result
(), because the location attribute is missing.

I don't think it's a huge loss to not be able to print the value of unused
variables, but I think that the example above is more problematic. Restoring
the previous behavior, even if accidental, would really help...

(thank you!)

[Bug bootstrap/55571] [4.6/4.7/4.8 regression] PR48076 fix broke bootstrap on armv5tel-linux-gnueabi

[brobecker at gnat dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55571



--- Comment #8 from Joel Brobecker  2012-12-04 
04:51:45 UTC ---

Created attachment 28869

  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28869

Small reproducer with arm-eabi



In case it's useful to anyone else, a small program that reproduces the

problem.



% arm-linux-gnueabi-gcc -o utils utils.c

[same problem with __sync_synchronize]

[Bug debug/61352] gcc 4.9.0 fails to execute dsymutil when linking executables on darwin

[brobecker at gnat dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61352

Joel Brobecker  changed:

   What|Removed |Added

 CC||brobecker at gnat dot com

--- Comment #13 from Joel Brobecker  ---
Sorry guys, but dsymutil is not working very well. I have a couple of examples
where, either dsymutil is excluding some DIEs from the DWARF image, or where
dsymutil actually segfaults. There is also the fact that dsymutil doesn't know
about recent DWARF enhancements, and doesn't work well when compiling code with
-gno-strict-dwarf.

GDB should be able to use the debug info from the object files without
requiring the use of dsymutil. Since we do not control dsymutil and its quality
level (or lack thereof), I suggest the best course of action is trying to
figure out why GDB doesn't pick the debugging info up from the .o files, and
then fix that.

In the meantime, I suggest we revert this change, or else make it optional at
the very least.

PS: Our experiments are on Darwin 13.4 and 14.3.