public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jeremy at goop dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/29305] local label-as-value being placed before function prolog Date: Sun, 01 Oct 2006 05:37:00 -0000 [thread overview] Message-ID: <20061001053651.15213.qmail@sourceware.org> (raw) In-Reply-To: <bug-29305-13334@http.gcc.gnu.org/bugzilla/> ------- 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 moderately subtle. If you don't intent to support my use-case, then gcc should warn/error-out rather than be quietly wrong. That said, I don't really understand why this can't be supported. In what way is this "not the correct way to think about what I'm doing"? How else should I achieve what I want? I should mention that this is Linux kernel code, and there are a number of places within the kernel where it would be useful to take the address of a particular statement without needing to "goto" to it, but have the code generated as if there is a goto (ie, merely taking the address of a label should be taken to be equivalent to actually having a goto to that label). -- jeremy at goop dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29305
next prev parent reply other threads:[~2006-10-01 5:37 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-01 4:33 [Bug c/29305] New: " jeremy at goop dot org 2006-10-01 4:43 ` [Bug c/29305] " pinskia at gcc dot gnu dot org 2006-10-01 5:18 ` jeremy at goop dot org 2006-10-01 5:29 ` [Bug middle-end/29305] " pinskia at gcc dot gnu dot org 2006-10-01 5:37 ` jeremy at goop dot org [this message] 2006-10-01 5:42 ` jeremy at goop dot org 2006-10-01 5:45 ` pinskia at gcc dot gnu dot org 2006-10-01 5:55 ` jeremy at goop dot org 2006-10-01 6:00 ` jeremy at goop dot org 2006-10-01 6:24 ` pinskia at gcc dot gnu dot org 2006-10-01 8:47 ` jeremy at goop dot org [not found] <bug-29305-4@http.gcc.gnu.org/bugzilla/> 2021-01-30 12:18 ` stsp at users dot sourceforge.net 2024-03-16 18:09 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20061001053651.15213.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).