mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mathieu Chouquet-Stringer <mchouque@free.fr>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
	rth@twiddle.net
Subject: Re: strncpy (maybe others) broken on Alpha
Date: Fri, 21 Apr 2006 13:55:56 +0200	[thread overview]
Message-ID: <20060421115556.GA14178@bigip.bigip.mine.nu> (raw)
In-Reply-To: <20060421114149.24F5EDBA1@gherkin.frus.com>

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]

On Fri, Apr 21, 2006 at 06:41:49AM -0500, Bob Tracy wrote:
> I'll try upgrading from gcc-4.0 to gcc-4.1, and if/when that has no
> effect, I'll go looking for a later binutils in Debian's "unstable"
> tree (I've already had to go to the "testing" tree to get beyond gcc-3
> and binutils-2.15.X).  Report to follow later today.

Ok.

> Item for consideration: what kind of optimization is enabled for your
> test case compile vs. what's being used for the kernel build?  That's
> another variable we need to sort out.  For what it's worth, I do *not*
> have CONFIG_CC_OPTIMIZE_FOR_SIZE enabled: the comment about "watch out
> for broken compilers" was enough to scare me off while we're trying to
> chase this down.

Well I thought of this already and tried my test case without any flags
but -Wall, with -O2 and -Os.  Same result.  I also compiled my test case
with the options used by the kernel (which ATM isn't compiled with -Os),
same thing.

I've attached to this email a tarball of what I use to test the
compiler/binutils.  It's faster than recompiling the whole kernel on
these slow machines!
-- 
Mathieu Chouquet-Stringer                           mchouque@free.fr

[-- Attachment #2: strncpy_debug.tar.gz --]
[-- Type: application/x-gzip, Size: 5065 bytes --]

  reply	other threads:[~2006-04-21 11:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 21:31 class_device_add error in SCSI with 2.6.17-rc2-g52824b6b Mathieu Chouquet-Stringer
2006-04-19 21:58 ` Bob Tracy
2006-04-19 22:17   ` Mathieu Chouquet-Stringer
2006-04-20 10:14   ` Mathieu Chouquet-Stringer
2006-04-20 10:57     ` Mathieu Chouquet-Stringer
2006-04-20 17:11     ` strncpy (maybe others) broken on Alpha Mathieu Chouquet-Stringer
2006-04-20 20:55       ` Mathieu Chouquet-Stringer
2006-04-20 21:24         ` Ivan Kokshaysky
2006-04-20 21:27           ` Mathieu Chouquet-Stringer
2006-04-20 21:40           ` Bob Tracy
2006-04-20 21:57           ` Mathieu Chouquet-Stringer
2006-04-21  2:43             ` Bob Tracy
2006-04-21  8:15               ` Mathieu Chouquet-Stringer
2006-04-21  9:21                 ` Mathieu Chouquet-Stringer
2006-04-21  9:50                   ` Mathieu Chouquet-Stringer
2006-04-21 11:41                     ` Bob Tracy
2006-04-21 11:55                       ` Mathieu Chouquet-Stringer [this message]
2006-04-21 14:22                         ` Ivan Kokshaysky
2006-04-21 19:37                           ` Bob Tracy
2006-04-21 21:12                             ` Ivan Kokshaysky
2006-04-21 22:49                               ` Bob Tracy
2006-04-22  8:47                                 ` Mathieu Chouquet-Stringer
2006-04-22  8:45                           ` Mathieu Chouquet-Stringer
2006-04-22 10:39                     ` Bryan Østergaard
2006-04-20 21:22       ` Ivan Kokshaysky
2006-04-20 21:25         ` Mathieu Chouquet-Stringer

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=20060421115556.GA14178@bigip.bigip.mine.nu \
    --to=mchouque@free.fr \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rct@gherkin.frus.com \
    --cc=rth@twiddle.net \
    /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®