public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gordon Sadler <gbsadler1@lcisp.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: debug/2968
Date: Mon, 13 Aug 2001 15:26:00 -0000	[thread overview]
Message-ID: <20010813222601.26235.qmail@sourceware.cygnus.com> (raw)

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

From: Gordon Sadler <gbsadler1@lcisp.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Cc:  
Subject: Re: debug/2968
Date: Mon, 13 Aug 2001 17:18:07 -0500

 On Mon, Aug 13, 2001 at 05:07:33PM -0400, Craig Rodrigues wrote:
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2968&database=gcc
 > 
 > If I compile your test case  with:
 > GNU C version 3.0.1 20010813
 > 
 > I get the following error:
 > ================================================================
 > printf_fp.c: In function `__printf_fp':
 > printf_fp.c:1144: Internal compiler error in gen_subprogram_die, at dwarf2out.c:9516
 > Please submit a full bug report,
 > with preprocessed source if appropriate.
 > ================================================================
 > 
 > 
 > If I compile your test case with:
 > GNU C version 3.1 20010811 (experimental)
 > 
 > Your test case successfully compiles and I do not get this error.
 > 
 I have no issue with mainline. However, the failure occurs on the branch
 which represents a regression from 2.95.x
 
 -- 
 Gordon Sadler
 


             reply	other threads:[~2001-08-13 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13 15:26 Gordon Sadler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-13 14:16 debug/2968 Craig Rodrigues
2001-06-02 10:06 debug/2968 hubicka

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=20010813222601.26235.qmail@sourceware.cygnus.com \
    --to=gbsadler1@lcisp.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).