public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/6300: sparcv9-sun-solaris2.7 gcc-3.1 C testsuite failure in gcc.dg/cpp/charconst.c Date: Sun, 21 Apr 2002 15:16:00 -0000 [thread overview] Message-ID: <20020421221601.13383.qmail@sources.redhat.com> (raw) The following reply was made to PR c/6300; it has been noted by GNATS. From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> To: zack@codesourcery.com Cc: gcc-gnats@gcc.gnu.org, neil@daikokuya.demon.co.uk Subject: Re: c/6300: sparcv9-sun-solaris2.7 gcc-3.1 C testsuite failure in gcc.dg/cpp/charconst.c Date: Sun, 21 Apr 2002 18:11:36 -0400 (EDT) > From: Zack Weinberg <zack@codesourcery.com> > > An i686-linux -> sparcv9-solaris2.7 cross compiler produces > > charconst.c:10:5: empty character constant > charconst.c:12:5: empty character constant > charconst.c:14:5: warning: character constant too long > charconst.c:16:5: warning: character constant too long > charconst.c:19:5: warning: multi-character character constant > charconst.c:24:11: empty character constant > charconst.c:25:7: empty character constant > charconst.c:27:7: warning: character constant too long > charconst.c:28:7: warning: character constant too long > charconst.c:31:7: warning: multi-character character constant > > which is the expected result. Can you still reproduce the problem? > zw Yes, however now it appears on plain sparc- targets, not sparcv9- because of some config.guess hackery that was eventually reverted. (See the 4/18 comment I added to the PR description field.) Sorry if this is confusing, but there was a short period where some unrelated patches were installed which changed the meaning of sparc- vs sparcv9- vs sparc64-. After the dust settled, it was reverted by rth. But I had reported the problem while my host temporarily called itself sparcv9-. Now that's gone and you should see the bug on sparc-sun-solaris2.7. I updated the PR to explain that but I guess I wasn't clear or needed to cc you directly. Sorry if I caused you to waste some time but hopefully you can reproduce the problem using the right target. --Kaveh -- Kaveh R. Ghazi Director of Systems Architecture ghazi@caip.rutgers.edu Qwest Global Services
next reply other threads:[~2002-04-21 22:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-21 15:16 Kaveh R. Ghazi [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-20 14:26 Zack Weinberg 2002-04-16 17:26 Kaveh R. Ghazi 2002-04-15 14:06 Kaveh R. Ghazi 2002-04-15 11:16 Neil Booth 2002-04-14 9:26 ghazi
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=20020421221601.13383.qmail@sources.redhat.com \ --to=ghazi@caip.rutgers.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).