https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29305
Andrew Pinski changed:
What|Removed |Added
Resolution|INVALID |DUPLICATE
--- Comment #12 from Andrew Pi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29305
Stas Sergeev changed:
What|Removed |Added
CC||stsp at users dot
sourceforge.net
--- Co
--- Comment #10 from jeremy at goop dot org 2006-10-01 08:47 ---
>In fact if GCC changes the behavior,
>it would be for the worse as then people using them correctly would be
>punished.
How so?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29305
--- Comment #9 from pinskia at gcc dot gnu dot org 2006-10-01 06:24 ---
(In reply to comment #8)
> Reopen as enhancement, in the hope gcc implements more useful semantics for
> taking the address of a label.
They are useful if used correctly. You are not using them correctly.
They are o
--- Comment #8 from jeremy at goop dot org 2006-10-01 05:58 ---
Reopen as enhancement, in the hope gcc implements more useful semantics for
taking the address of a label.
--
jeremy at goop dot org changed:
What|Removed |Added
--
--- Comment #7 from jeremy at goop dot org 2006-10-01 05:55 ---
Subject: Re: local label-as-value being placed before
function prolog
pinskia at gcc dot gnu dot org wrote:
> what do you really want? Because what you have mentioned so far seems like
> you
> should be writting a .s fi
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-10-01 05:45 ---
(In reply to comment #4)
> Well, it isn't failing in any obvious fashion. It's quietly putting the label
> at the wrong place, without complaint.
There is no wrong place if you don't use it via a local computed go
--- Comment #5 from jeremy at goop dot org 2006-10-01 05:42 ---
Created an attachment (id=12363)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12363&action=view)
More complete example of what I'm trying to do
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29305
--- Comment #4 from jeremy at goop dot org 2006-10-01 05:36 ---
Well, it isn't failing in any obvious fashion. It's quietly putting the label
at the wrong place, without complaint. The same code later in a function does
put the labels at the right place, so the failure mode is moderate
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-10-01 05:29 ---
It is failing right out if you don't have any computed gotos in your function
(or a goto to that label).
You should try doing:
asm volatile("faulted: ud2");
and make faulted a static function but that might not work
10 matches
Mail list logo