public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp 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: Thu, 15 Jun 2006 17:15:00 -0000 [thread overview] Message-ID: <20060615165012.22939.qmail@sourceware.org> (raw) In-Reply-To: <bug-27528-11706@http.gcc.gnu.org/bugzilla/> ------- Comment #12 from hp at gcc dot gnu dot org 2006-06-15 16:50 ------- In reply to comment #11, "i" *is* an appropriate constraint, if any. I see the problem with the reduced test-case in comment #3, so I'm going to limit the scope of my involvement to fixing that. Hopefully we can leave the discussion on macro expansion for now, or at least any specific problems with e.g. __FUNCTION__ would be subject to a separate PR. (Though it's interesting if it works but __FILE__ doesn't.) The address of a string constant is for all normal use expressed as a local label, hence "symbolic constant" when it comes to assembly code. As a GCC backend guy, I know that "i" is a constraint useful in a GCC machine description when there's any constant symbol or label, possibly offset by a numeric constant. (Constraints are used for both machine descriptions and asms.) Besides bug.h in asm-ppc and asm-ppc64, I see this construct for asm-x86_64, asm-alpha, asm-ppc64, asm-i386 too. Not as not an argument for correctness, just an observation that contradicts the "only used with powerpc" statement. That is, except for use of __FUNCTION__. Hm. I think I need reconfirmation that we see the same problem: Is the code in comment #3 really a reduced test-case, i.e. does the code in comment #3 cause a warning for the compiler and options (filename replaced) for which you originally reported the problem? (If not, I'd like to know for what version it causes the same warning.) Thanks for your patience. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27528
next prev parent reply other threads:[~2006-06-15 16:50 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 [this message] 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 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=20060615165012.22939.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).