--- Comment #6 from steven at gcc dot gnu dot org 2009-02-22 16:36 ---
Locations are now handled differently (mapped locations).
--
steven at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #5 from barbieri at gmail dot com 2005-12-24 22:47 ---
any news on this front?
I'll present a tutorial in LinuxConf.au and need to know if front-end should
provide the information or middle-end should handle it.
In both cases I'll provide the patch to gcc, but I need to kno
--- Comment #4 from barbieri at gmail dot com 2005-12-07 10:49 ---
So, this is a bug.
I just need a confirmation if it's a bug in the middle-end layer, so there is
already a patch, or if this is a bug in the front-end, then I will add the
check to the gimplify code.
Since there is no d
--- Comment #3 from barbieri at gmail dot com 2005-11-18 18:36 ---
Created an attachment (id=10276)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10276&action=view)
gcc-lower_function_body.patch
Alternative patch that also fix seg fault, but earlier.
It's uglier than the previous
--- Comment #2 from pinskia at gcc dot gnu dot org 2005-11-18 18:17 ---
Actually this should never happen in general. Your front-end really should be
adding locus on the statements.
I will let someone else decide if this is a real middle-end bug or a bug in
your front-end.
I should no
--- Comment #1 from barbieri at gmail dot com 2005-11-18 18:09 ---
Created an attachment (id=10274)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10274&action=view)
gcc-annotate_with_file_line.patch
Fix segfault
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24932
