public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/27528] compiling linux kernels 2.6.16.14/15 2.6.17-rc3 on powerpc (7450) get error on long exixting code
Date: Fri, 03 Nov 2006 13:23:00 -0000	[thread overview]
Message-ID: <20061103132333.31403.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27528-11706@http.gcc.gnu.org/bugzilla/>



------- Comment #16 from rsandifo at gcc dot gnu dot org  2006-11-03 13:23 -------
I'm testing a possible patch.  I didn't want to reassign the bug
to myself in case H-P is still looking at it too.

At this stage I have no idea how successful the patch will be.
It seems to me that, as with most other gcc extensions, the "right"
behaviour isn't really defined here.  The warning and error don't
seem unreasonable from a gcc hacker's perspective, but I can see why
users would expect it to work.  My main fear is that, even if the
patch survives the normal testing (and a kernel build, which I
intend to try too), it could easily break another unstated
assumption in other user code.

Richard


-- 


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


  parent reply	other threads:[~2006-11-03 13:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10  2:44 [Bug c/27528] New: " malitzke at metronets dot com
2006-05-10  3:05 ` [Bug c/27528] " malitzke at metronets dot com
2006-05-10  4:04 ` [Bug middle-end/27528] " pinskia at gcc dot gnu dot org
2006-05-10  5:24 ` pinskia at gcc dot gnu dot org
2006-05-10  5:30 ` pinskia at gcc dot gnu dot org
2006-05-10 14:44 ` malitzke at metronets dot com
2006-05-10 14:56 ` dje at gcc dot gnu dot org
2006-05-10 15:06 ` pinskia at gcc dot gnu dot org
2006-05-10 20:17 ` malitzke at metronets dot com
2006-05-10 20:41 ` pinskia at gcc dot gnu dot org
2006-06-14 15:09 ` hp at gcc dot gnu dot org
2006-06-14 15:09 ` hp at gcc dot gnu dot org
2006-06-15  3:26 ` malitzke at metronets dot com
2006-06-15 17:15 ` hp at gcc dot gnu dot org
2006-06-15 23:03 ` malitzke at metronets dot com
2006-06-15 23:03   ` Andrew Pinski
2006-06-15 23:07 ` pinskia at physics dot uc dot edu
2006-10-27  5:24 ` pinskia at gcc dot gnu dot org
2006-11-03 13:23 ` rsandifo at gcc dot gnu dot org [this message]
2006-11-03 13:27 ` hp at gcc dot gnu dot org
2006-11-03 13:30 ` rsandifo at gcc dot gnu dot org
2006-11-09  9:34 ` rsandifo at gcc dot gnu dot org
2006-11-11  9:47 ` rsandifo at gcc dot gnu dot org
2006-11-11  9:53 ` rsandifo at gcc dot gnu dot org
2006-11-11  9:54 ` rsandifo at gcc dot gnu dot org
2006-12-01  1:07 ` chaoyingfu at gcc dot gnu dot org
2007-01-10 19:14 ` [Bug middle-end/27528] [4.2/4.3 Regression] " pinskia at gcc dot gnu dot 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=20061103132333.31403.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).