public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/32772] [4.3 Regression] error: found real variable when subvariables should have appeared
Date: Tue, 04 Sep 2007 06:48:00 -0000	[thread overview]
Message-ID: <20070904064818.2276.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32772-9876@http.gcc.gnu.org/bugzilla/>



------- Comment #12 from jakub at gcc dot gnu dot org  2007-09-04 06:48 -------
Which testcase is not fixed?

./xgcc -B ./ -Wall -Wundef -m32 -Wstrict-prototypes -Wno-trigraphs
-fno-strict-aliasing -fno-common -Werror-implicit-function-declaration
-Werror-implicit-function-declaration -Os -msoft-float -mregparm=3
-freg-struct-return -mpreferred-stack-boundary=2 -march=athlon -ffreestanding
-maccumulate-outgoing-args -fno-omit-frame-pointer -fno-optimize-sibling-calls
-fasynchronous-unwind-tables  -fno-stack-protector pr32772-1.i -S
In file included from include/asm/thread_info.h:17,
                 from include/linux/thread_info.h:22,
                 from include/linux/preempt.h:10,
                 from include/linux/spinlock.h:50,
                 from include/linux/mmzone.h:8,
                 from include/linux/gfp.h:5,
                 from include/linux/mm.h:9,
                 from mm/page_alloc.c:19:
include/asm/processor.h: In function `cpuid_count':
include/asm/processor.h:622: warning: pointer targets in passing argument 1 of
`__cpuid' differ in signedness
include/asm/processor.h:622: warning: pointer targets in passing argument 2 of
`__cpuid' differ in signedness
include/asm/processor.h:622: warning: pointer targets in passing argument 3 of
`__cpuid' differ in signedness
include/asm/processor.h:622: warning: pointer targets in passing argument 4 of
`__cpuid' differ in signedness

succeeds on the http://gcc.gnu.org/bugzilla/attachment.cgi?id=13918&action=view
testcase, and the http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32772#c6 testcase
as well.


-- 


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


  parent reply	other threads:[~2007-09-04  6:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-15 23:41 [Bug c/32772] New: " bunk at stusta dot de
2007-07-15 23:56 ` [Bug c/32772] " bunk at stusta dot de
2007-07-15 23:59 ` bunk at stusta dot de
2007-07-16  0:22 ` [Bug tree-optimization/32772] " pinskia at gcc dot gnu dot org
2007-07-16 10:04 ` rguenth at gcc dot gnu dot org
2007-07-16 10:17 ` rguenth at gcc dot gnu dot org
2007-07-16 10:17 ` rguenth at gcc dot gnu dot org
2007-07-16 14:03 ` jakub at gcc dot gnu dot org
2007-08-04 12:06 ` pinskia at gcc dot gnu dot org
2007-08-10  0:46 ` mmitchel at gcc dot gnu dot org
2007-08-19 23:24 ` dberlin at gcc dot gnu dot org
2007-08-20  1:55 ` dberlin at gcc dot gnu dot org
2007-08-23 12:44 ` rguenth at gcc dot gnu dot org
2007-08-23 13:46 ` dberlin at gcc dot gnu dot org
2007-09-04  6:48 ` jakub at gcc dot gnu dot org [this message]
2007-09-04  8:22 ` jakub at gcc dot gnu dot org
2007-09-07  0:17 ` pinskia at gcc dot gnu dot org
2007-09-23  9:45 ` jakub 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=20070904064818.2276.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).