From: Phil Blundell <pb@pbcl.net>
To: Holger Freyther <holger@freyther.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: kernel miscompilation with gcc 4.8 for ARMv5
Date: Fri, 19 Jul 2013 12:24:50 +0100 [thread overview]
Message-ID: <1374233090.6324.26.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <loom.20130719T072922-639@post.gmane.org>
On Fri, 2013-07-19 at 05:39 +0000, Holger Freyther wrote:
> will crash on the above line. Compiling tcp_ipv4.c with GCC4.6.3
> and re-linking doesn't appear to fix the problem but maybe I made
> another mistake.
If your analysis of the path that leads up to the crash is correct then
it sounds like the bug is probably in inet_hashtables.c not tcp_ipv4.c.
Does it help if you recompile that one file with the older GCC and
re-link?
p.
prev parent reply other threads:[~2013-07-19 11:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 11:36 kernel miscompilation with gcc 4.8 for ARMv5 Enrico Scholz
2013-07-10 12:34 ` Enrico Scholz
2013-07-10 13:15 ` Mike Looijmans
2013-07-10 13:25 ` Mark Hatle
2013-07-11 5:38 ` Mike Looijmans
2013-07-10 13:57 ` Bruce Ashfield
2013-07-10 14:30 ` Enrico Scholz
2013-07-10 16:35 ` Bruce Ashfield
2013-07-14 4:58 ` Bruce Ashfield
2013-07-19 5:39 ` Holger Freyther
2013-07-19 11:24 ` Phil Blundell [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=1374233090.6324.26.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=holger@freyther.de \
--cc=openembedded-core@lists.openembedded.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