public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Christoph Ludwig <cludwig@cdc.informatik.tu-darmstadt.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/8541: Alpha architecture: Wrong code with -O1 and higher (Regression from 2.95)
Date: Tue, 19 Nov 2002 14:36:00 -0000	[thread overview]
Message-ID: <20021112130606.1750.qmail@sources.redhat.com> (raw)

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

From: Christoph Ludwig <cludwig@cdc.informatik.tu-darmstadt.de>
To: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: optimization/8541: Alpha architecture: Wrong code with -O1 and higher (Regression from 2.95)
Date: Tue, 12 Nov 2002 14:00:57 +0100

 On Tue, Nov 12, 2002 at 01:01:25PM +0100, Falk Hueffner wrote:
 > 
 >   // a1 * RADIX + a0 = quot * b + RV
 >   inline udigit
 >   divide (udigit & quot, udigit a1, udigit a0, udigit b)
 >   {
 >     udigit a[2] = { a0, a1 };
 >     return mpn_divrem_1(&quot, 0, a, 2, b);
 >   }
 > 
 > [...]
 >     udigit accum_l, accum_h, temp_h, temp_l, carry;
 > [...]
 >       accum_h = divide(carry, 0, accum_h, pp);
 > 
 > It seems to me that mpn_divrem_1 might write 2 words to carry,
 > clobbering random stack memory. Are you sure it doesn't?
 
 Oops! I added a few further tests, and it seems, you are right.
 I was looking for the error in the wrong corner of the library. :-(
 
 My apologies for the unnecessary noise on the gcc bug mailing
 list. How do I withdraw a bug report or request it to be closed?
 
 Regards
 
 Christoph
 -- 
 http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/cludwig.html
 LiDIA-CA: http://www.informatik.tu-darmstadt.de/TI/Forschung/LiDIA-CA/
 


             reply	other threads:[~2002-11-12 13:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 14:36 Christoph Ludwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-22 17:16 bangerth
2002-11-19 15:07 Christian Cornelssen
2002-11-19 14:16 Falk Hueffner
2002-11-19 13:26 cludwig

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=20021112130606.1750.qmail@sources.redhat.com \
    --to=cludwig@cdc.informatik.tu-darmstadt.de \
    --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).