public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ebotcazou@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	urazov@yahoo.com
Subject: Re: c/10365: Seems like bug in code generator on Sun Sparc (Sol;aris 8) platform
Date: Sat, 12 Apr 2003 20:27:00 -0000	[thread overview]
Message-ID: <20030412202727.6144.qmail@sources.redhat.com> (raw)

Synopsis: Seems like bug in code generator on Sun Sparc (Sol;aris 8) platform

State-Changed-From-To: open->feedback
State-Changed-By: ebotcazou
State-Changed-When: Sat Apr 12 20:27:27 2003
State-Changed-Why:
    Tough bug :-)
    I was able to construct a self-contained testcase, but it doesn't fail on
    SunOS gax 5.8 Generic_108528-16 sun4u sparc SUNW,Ultra-2
    with GCC 3.2.1 and GCC 3.2.2
    
    Could you try to build a self-contained testcase yourself?
    Begin with the test program and gradually import the required
    functions from the library sources, verifying each time that
    the test still fails.
    
    Thanks in advance.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10365


             reply	other threads:[~2003-04-12 20:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12 20:27 ebotcazou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-12 20:07 ebotcazou
2003-04-11 21:26 Yuri Urazov
2003-04-11 21:26 Yuri Urazov
2003-04-11 21:26 Yuri Urazov
2003-04-11 21:16 Yuri Urazov
2003-04-11  9:02 ebotcazou
2003-04-11  8:38 ebotcazou
2003-04-11  8:37 ebotcazou
2003-04-10  7:06 Eric Botcazou
2003-04-09 22:36 Yuri Urazov
2003-04-09 22:36 Yuri Urazov
2003-04-09 22:36 Yuri Urazov
2003-04-09 21:01 bangerth
2003-04-09 20:16 urazov

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=20030412202727.6144.qmail@sources.redhat.com \
    --to=ebotcazou@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=urazov@yahoo.com \
    /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).