public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: pkoning@xedia.com (Paul Koning)
Cc: robertl@dgii.com, egcs@cygnus.com
Subject: Re: Bug on PPC (no patch yet)
Date: Tue, 21 Oct 1997 13:32:00 -0000	[thread overview]
Message-ID: <199710212022.NAA23019@atrus.synopsys.com> (raw)
In-Reply-To: <9710212002.AA14764@kona.>

>  Robert> + /* If type is negative, produce an internal compiler error.
>  Robert> + This may be caused by an array that is too large.

As I said, I'm not sure that patch is correct, since a larger overflow
can produce an invalid positive result.

> I assume this wouldn't happen for 64-bit targets unless the array size
> exceeds 64 (not 32) bits, right?

Yes.

> The error generated should NOT be "internal compiler error".  That
> error message should always mean "there's a bug in the compiler" and
> never "there's something wrong with your source code".

There's nothing wrong with the source code.  Furthermore, the compiler is
not detecting an error in itself, so it's not an internal compiler error
either.  That's why I suggested a "sorry, not implemented" type of
message.


  reply	other threads:[~1997-10-21 13:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-20 13:24 Elliot Lee
1997-10-21  8:35 ` Jeffrey A Law
1997-10-21  9:08   ` Joe Buck
1997-10-21  9:39     ` Ian Lance Taylor
1997-10-21  9:39       ` Joe Buck
1997-10-21  9:43     ` Robert Lipe
1997-10-21 13:08       ` Paul Koning
1997-10-21 13:32         ` Joe Buck [this message]
1997-10-21 13:48         ` mongo array/bitfield errors Was: " Robert Lipe
1997-10-21 15:50         ` Richard Henderson

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=199710212022.NAA23019@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=egcs@cygnus.com \
    --cc=pkoning@xedia.com \
    --cc=robertl@dgii.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).