public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Torbjorn Granlund <tege@swox.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/8819: [sparc] G++ generates code with unresolved internal label
Date: Thu, 27 Mar 2003 12:26:00 -0000	[thread overview]
Message-ID: <20030327115600.2947.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

The following reply was made to PR target/8819; it has been noted by GNATS.

From: Torbjorn Granlund <tege@swox.com>
To: ebotcazou@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	gcc-gnats@gcc.gnu.org
Subject: Re: target/8819: [sparc] G++ generates code with unresolved internal label
Date: 27 Mar 2003 12:55:48 +0100

 ebotcazou@gcc.gnu.org writes:
 
   Old Synopsis: [sparc solaris] G++ generates code with unresolved internal label
   New Synopsis: [sparc] G++ generates code with unresolved internal label
   
   State-Changed-From-To: open->feedback
   State-Changed-By: ebotcazou
   State-Changed-When: Thu Mar 27 11:12:21 2003
   State-Changed-Why:
       I can't reproduce with gcc 3.2.1 or gcc 3.2.2 on SunOS vegeta 5.7 Generic_106541-23 sun4u sparc SUNW,Ultra-2.
   
   http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8819
   
 
 Have you tried reproducing it with the setup suggested in the
 PR?  As I trust you know, a different compiler version might
 not stumple on a certain test case, even if the bug is still there.
 
 -- 
 Torbjörn


             reply	other threads:[~2003-03-27 11:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27 12:26 Torbjorn Granlund [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-27 13:07 Eric Botcazou
2003-03-27 11:31 ebotcazou

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=20030327115600.2947.qmail@sources.redhat.com \
    --to=tege@swox.com \
    --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: 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).