From: Rich Baum <richbaum@acm.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, richbaum@acm.org (Rich Baum)
Cc: linux-kernel@vger.kernel.org,
torvalds@transmeta.com (Linus Torvalds),
alan@lxorguk.ukuu.org.uk (Alan Cox)
Subject: Re: [PATCH] warning fixes for 2.4.5pre5
Date: Fri, 25 May 2001 15:47:29 -0500 [thread overview]
Message-ID: <8860416539B@coral.indstate.edu> (raw)
In-Reply-To: <E153KAG-0006k7-00@the-village.bc.nu>
In-Reply-To: <E153KAG-0006k7-00@the-village.bc.nu>
On Friday 25 May 2001 11:10 am, Alan Cox wrote:
> > This patch has been tested and the code does compile.
> >
> > Rich
> >
> > diff -urN -X /linux/dontdiff linux/arch/i386/math-emu/fpu_trig.c
> > rb/arch/i386/math-emu/fpu_trig.c
> > --- linux/arch/i386/math-emu/fpu_trig.c Fri Apr 6 12:42:47 2001
> > +++ rb/arch/i386/math-emu/fpu_trig.c Tue May 22 16:44:57 2001
> > @@ -1543,6 +1543,7 @@
> > EXCEPTION(EX_INTERNAL | 0x116);
> > return;
> > #endif /* PARANOID */
> > + return;
>
> This seems to be a change in behaviour. Have you done a glibc fpu test on
> the changes ?
I used objdump on the fpu_trig.o files in both trees and they do differ.
When I use break instead of return in my tree the two files are the same.
Here is a revised patch that fixes the warning and produces the same assembly
code code as the version in Linus' tree.
diff -urN -X /linux/dontdiff linux/arch/i386/math-emu/fpu_trig.c
rb/arch/i386/math-emu/fpu_trig.c
--- linux/arch/i386/math-emu/fpu_trig.c Fri Apr 6 12:42:47 2001
+++ rb/arch/i386/math-emu/fpu_trig.c Tue May 22 16:44:57 2001
@@ -1543,6 +1543,7 @@
EXCEPTION(EX_INTERNAL | 0x116);
return;
#endif /* PARANOID */
+ break;
prev parent reply other threads:[~2001-05-25 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 2:40 [PATCH] warning fixes for 2.4.5pre5 Rich Baum
2001-05-25 15:13 ` Juan Quintela
2001-05-25 15:42 ` Alan Cox
2001-05-25 16:10 ` Alan Cox
2001-05-25 20:47 ` Rich Baum [this message]
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=8860416539B@coral.indstate.edu \
--to=richbaum@acm.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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