public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/3906: Internal compiler error in change_address, at emit-rtl.c:1635
Date: Wed, 07 Nov 2001 06:17:00 -0000	[thread overview]
Message-ID: <20011117064603.10741.qmail@sourceware.cygnus.com> (raw)

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

From: Craig Rodrigues <rodrigc@mediaone.net>
To: Tanmoy Bhattacharya <tanmoy@qcd.lanl.gov>
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: optimization/3906: Internal compiler error in change_address, at emit-rtl.c:1635
Date: Mon, 13 Aug 2001 18:52:41 -0400

 On Mon, Aug 13, 2001 at 04:43:57PM -0600, Tanmoy Bhattacharya wrote:
 > I could probably provide a C++ example, but I do not have the time to
 > test right now.  But a C compiler *must* compile every strictly
 > conforming C program, which this one becomes if one supplies
 > definitions for main and setloglim, possibly in a separate translation
 > unit. 
 
 OK,
 
 If I compile your example with:
 gcc version 3.0.1 20010813 (prerelease)
 
 and use:
 gcc -O -c example.i
 
 I do not get any compiler errors.
 
 Can you try again, perhaps with a newer Solaris 8 gcc snapshot from:
 http://www.codesourcery.com/gcc_binary_snapshots/
 -- 
 Craig Rodrigues        
 http://www.gis.net/~craigr    
 rodrigc@mediaone.net          


             reply	other threads:[~2001-11-17  6:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07  6:17 Craig Rodrigues [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-25  5:14 rodrigc
2001-11-25  4:26 rodrigc
2001-11-07  3:29 Tanmoy Bhattacharya
2001-08-13 15:24 rodrigc
2001-07-31 17:16 tanmoy

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=20011117064603.10741.qmail@sourceware.cygnus.com \
    --to=rodrigc@mediaone.net \
    --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).