From: David Relson <relson@osagesoftware.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Compilation problem in ndisc.c / 2.5.1-pre2 : possible gcc bug?
Date: Wed, 28 Nov 2001 14:29:07 -0500 [thread overview]
Message-ID: <4.3.2.7.2.20011128142619.00b1a380@mail.osagesoftware.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1011128140806.5756A-100000@chaos.analogic.co m>
In-Reply-To: <slrna0ad1m.4ia.spamtrap@dexter.hensema.xs4all.nl>
At 02:09 PM 11/28/01, you wrote:
>On 28 Nov 2001, Erik Hensema wrote:
>
> >
> > I've been looking into the compile problems of net/ipv6/ndisc.c in
> > 2.5.1-pre2 and I found that the asm generated by gcc (2.95.3) is wrong:
> >
> > This is a small part of a diff betweem two asm files generated by gcc, note
> > the missing \n's in the wrong code:
> >
> > -
> > - addl 0(%ebp), %edx
> > - adcl 4(%ebp), %edx
> > - adcl 8(%ebp), %edx
> > - adcl 12(%ebp), %edx
> > - adcl 0(%ecx), %edx
> > - adcl 4(%ecx), %edx
> > - adcl 8(%ecx), %edx
> > - adcl 12(%ecx), %edx
> > - adcl %edi, %edx
> > - adcl %eax, %edx
> > - adcl $0, %edx
> > -
> > + addl 0(%ebp), %edxadcl 4(%ebp), %edxadcl 8(%ebp), %edxadcl
> 12(%ebp), %edxadcl 0(%ecx), %edxadcl 4(%ecx), %edxadcl 8(%ecx), %edxadcl
> 12(%ecx), %edxadcl %edi, %edxadcl %eax, %edxadcl $0, %edx
>
>
>This is probably just some loop unrolling, not some as you say "wrong
>code".
The lack of \n's is wrong. Adding \n's and some whitespace, gives
identical code. Looks like a defective printf() in gcc.
David
prev parent reply other threads:[~2001-11-28 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.95.1011128140806.5756A-100000@chaos.analogic.co m>
2001-11-28 19:00 ` Erik Hensema
2001-11-28 19:09 ` Richard B. Johnson
2001-11-28 19:39 ` Martin Eriksson
2001-11-28 19:51 ` Richard B. Johnson
2001-11-28 20:08 ` Brian Gerst
2001-11-28 21:04 ` PATCH: " Erik Hensema
2001-11-29 14:07 ` Richard B. Johnson
2001-11-28 19:29 ` David Relson [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=4.3.2.7.2.20011128142619.00b1a380@mail.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®