public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sparc64 at rediffmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/28581] Illegal loading the address of a label with -O2
Date: Sun, 18 Nov 2007 14:44:00 -0000	[thread overview]
Message-ID: <20071118144426.2884.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28581-5993@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from sparc64 at rediffmail dot com  2007-11-18 14:44 -------
> I agree that we should clarify the documentation if we definitely rule the
> code as being invalid.

Since "&&" is a C extension, I believe one can reserve the right to limit how
long it extends. But this limitation, which hits only when "optimization" kicks
in is very very misleading. And, I find such a limitation spoiling the whole
idea of having the extension.

For example, the original post posted by "inaoka" tries to pass a pointer
loaded with "&&" extension. And, he has run into trouble.

The point here is that the "Optimization" rule is very quick to rule out that
the usage of "&&" is only for "goto"s. This precludes a beautiful C extension
from being as beautiful as it ought to be.

It would be really nice on the part of GCC developers to fix this. I am sure
this must be a very small thing to fix (apologies if not).

Thanks


-- 


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


  parent reply	other threads:[~2007-11-18 14:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03  6:03 [Bug c/28581] New: " inaoka dot kazuhiro at renesas dot com
2006-08-03  6:07 ` [Bug c/28581] " inaoka dot kazuhiro at renesas dot com
2006-08-03 11:45 ` [Bug middle-end/28581] " pinskia at gcc dot gnu dot org
2006-08-08  0:33 ` pinskia at gcc dot gnu dot org
2007-11-16 19:58 ` pinskia at gcc dot gnu dot org
2007-11-17 11:50 ` sparc64 at rediffmail dot com
2007-11-17 20:36 ` pinskia at gcc dot gnu dot org
2007-11-18  6:41 ` sparc64 at rediffmail dot com
2007-11-18  7:25 ` sparc64 at rediffmail dot com
2007-11-18  7:28 ` sparc64 at rediffmail dot com
2007-11-18  8:46 ` ebotcazou at gcc dot gnu dot org
2007-11-18 14:44 ` sparc64 at rediffmail dot com [this message]
2007-11-18 16:05 ` steven at gcc dot gnu dot org
     [not found] <bug-28581-4@http.gcc.gnu.org/bugzilla/>
2021-07-21 16:15 ` schwab@linux-m68k.org
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=20071118144426.2884.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: link
Be 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).