From: Andrew Stubbs <ams@codesourcery.com>
To: linux-sh@vger.kernel.org
Subject: Re: Sourcery G++ 4.4-136 Release
Date: Thu, 01 Apr 2010 07:36:13 +0000 [thread overview]
Message-ID: <4BB44CED.3020507@codesourcery.com> (raw)
In-Reply-To: <201003271507.12509.fabio.giovagnini@aurion-tech.com>
On 01/04/10 08:19, Fabio Giovagnini wrote:
> Hi Andrew, what are
> sh-uclinux-ld: Warning: size of symbol `sys_connect' changed from 12 in
> kernel/built-in.o to 164 in net/built-in.o
> sh-uclinux-ld: Warning: size of symbol `sys_socketpair' changed from 12 in
> kernel/built-in.o to 312 in net/built-in.o
> sh-uclinux-ld: Warning: size of symbol `sys_getpeername' changed from 12 in
> kernel/built-in.o to 164 in net/built-in.o
This means that some of the COMDAT sections did not match exactly when
the linker tried to unify them.
Basically, both the files have a copy of what is supposedly the exact
same code. The linker then chooses one, it doesn't matter which, and
discards the others. However, the linker first does a few sanity checks
to make sure they are the same, and in this case it has found that they
are not.
This can be caused in one of two ways:
1. The sections were compiled from different source code (with the same
name). This is a user mistake and results in undefined behaviour.
2. The same source was compiled with different optimization and/or other
compiler parameters. This is typically harmless.
The problem might be a latent bug in the kernel build system, or it
might be a toolchain bug. I don't know yet.
Either way, my kernel built with many of those warnings, but it seems to
run fine.
Andrew
prev parent reply other threads:[~2010-04-01 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201003221942.o2MJgBRf028294@spugna.yepa.com>
[not found] ` <201003260659.57890.fabio.giovagnini@aurion-tech.com>
[not found] ` <4BAC84F1.2070106@codesourcery.com>
2010-03-27 14:07 ` Sourcery G++ 4.4-136 Release Fabio Giovagnini
2010-03-27 14:07 ` Fabio Giovagnini
2010-04-01 7:19 ` Fabio Giovagnini
2010-04-01 7:36 ` Andrew Stubbs [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=4BB44CED.3020507@codesourcery.com \
--to=ams@codesourcery.com \
--cc=linux-sh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.