From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: binutils <binutils@sourceware.org>,
amodra@gmail.com, "H.J. Lu" <hjl.tools@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Release 2.21.1 ?
Date: Wed, 16 Mar 2011 15:34:00 -0000 [thread overview]
Message-ID: <AANLkTikHGo+pgTGxBZq=-LZt-iVFr1Q9FywTuhPNbE_B@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik43A0ckO0hDVYakvpWY39nroXgqret+yvbFS-h@mail.gmail.com>
On Wed, Mar 16, 2011 at 10:37 AM, Sedat Dilek
<sedat.dilek@googlemail.com> wrote:
> On Wed, Mar 16, 2011 at 9:50 AM, Tristan Gingold <gingold@adacore.com> wrote:
>>
>> On Mar 16, 2011, at 7:44 AM, Sedat Dilek wrote:
>>
>>> Hi,
>>>
>>> while handling several breakages in linux-next kernel, it showed PR
>>> gas/12519 (see [1]) is somehow incomplete as it gives no pointer to
>>> the symbol name in case of an error.
>>> "Mention symbol name in non-constant .size expression." (see [2]) as a
>>> follow-up patch definitely helps to enlighten developer's where to dig
>>> into occuring problems.
>>> "Revert the last change on gas/elf/bad-size.err." (see [3]) is a fixup to [2].
>>>
>>> It would be nice to see [2] and [3] backported to 2.21-branch.
>>
>> Why not.
>>
>> Does it make sense to generate a warning instead of an error in 2.21.1 for backward bug-compatibility ?
>> Alan, what's your opinion ?
>>
>> Tristan.
>>
>>
>
> H.J. offered a proposal patch ("PATCH: Add
> --size-check=[error|warning]") [1] with an easy switch opportunity and
> H. Peter Anvin illustrated how the warning switch can be used from
> command-line [2].
>
> IIRC there was no official decision what will be the default behaviour:
> binutils developers mostly advocate "error" as default, whereas a lot
> of Linux kernel developers want "warning" as default.
>
> Unfortunately, I could not apply (and test) H.J.'s proposal patch and
> requested a proper one [3].
>
> - Sedat -
>
>
> [1] http://sourceware.org/ml/binutils/2011-03/msg00214.html
> [2] http://sourceware.org/ml/binutils/2011-03/msg00283.html
> [3] http://sourceware.org/ml/binutils/2011-03/msg00263.html
>
Hi,
I have cherry-picked commit 8bba209217cab2e7fb949768ffc4a5d40ecc144a
("Add --size-check=[error|warning].") from upstream and built a Debian
package on top of binutils (2.21.0.20110302-2) source package.
I returned to the linux-next (next-20110308) which I reported as
"broken" and currently building a new kernel (it's not finished yet,
make -j=1).
Instructions:
$ cd $BUILD_DIR
$ make CC='gcc -Wa,--size-check=warning'
Check current build-log:
$ egrep 'Assembler messages:|Warning: .size expression with symbol'
build.log
/home/sd/src/linux-2.6/linux-2.6.38-rc7/debian/build/source_i386_none/arch/x86/kernel/entry_32.S:
Assembler messages:
/home/sd/src/linux-2.6/linux-2.6.38-rc7/debian/build/source_i386_none/arch/x86/kernel/entry_32.S:1421:
Warning: .size expression with symbol `apf_page_fault' does not
evaluate to a constant
/home/sd/src/linux-2.6/linux-2.6.38-rc7/debian/build/source_i386_none/arch/x86/kernel/acpi/wakeup_rm.S:
Assembler messages:
/home/sd/src/linux-2.6/linux-2.6.38-rc7/debian/build/source_i386_none/arch/x86/kernel/acpi/wakeup_rm.S:12:
Warning: .size expression with symbol `wakeup_code_start' does not
evaluate to a constant
...
Nice, it works as expected :-).
( These were the two places I discovered, but this time the kernel
building is not interrupted. )
/me is just fine with the default behaviour of (my freshly-built)
binutils/as "--size-check=error".
Thanks to all involved people for their help, especially to H.J. for
providing a patch and solution!
Regards,
- Sedat -
P.S.: These 3 patches should be backported to 2.21-branch.
$ LC_ALL=C ls -l patches
total 16
-rw-r--r-- 1 sd sd 3137 Mar 16 14:45
0001-Mention-symbol-name-in-non-constant-.size-expression.patch
-rw-r--r-- 1 sd sd 948 Mar 16 14:45
0002-Revert-the-last-change-on-gas-elf-bad-size.err.patch
-rw-r--r-- 1 sd sd 7782 Mar 16 14:45 0003-Add-size-check-error-warning.patch
next prev parent reply other threads:[~2011-03-16 15:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 6:44 Sedat Dilek
2011-03-16 8:50 ` Tristan Gingold
2011-03-16 9:37 ` Sedat Dilek
2011-03-16 15:34 ` Sedat Dilek [this message]
2011-03-16 12:17 ` Alan Modra
2011-03-16 12:44 ` H.J. Lu
2011-03-16 12:47 ` Tristan Gingold
-- strict thread matches above, loose matches on Subject: below --
2011-03-15 8:21 Tristan Gingold
2011-03-15 13:24 ` Ian Lance Taylor
2011-03-15 17:28 ` Jakub Jelinek
2011-03-15 17:30 ` Matthias Klose
2011-03-15 17:51 ` Dave Korn
2011-03-16 7:52 ` Tristan Gingold
2011-03-16 4:03 ` Mike Frysinger
2011-03-16 8:49 ` Tristan Gingold
2011-03-16 12:19 ` Alan Modra
2011-03-17 12:21 ` Alan Modra
2011-03-17 12:39 ` Tristan Gingold
2011-03-20 21:41 ` Mike Frysinger
2011-03-23 16:00 ` Tristan Gingold
2011-05-16 7:47 ` Andreas Krebbel
2011-05-16 7:53 ` Tristan Gingold
2011-05-17 17:31 ` Andreas Krebbel
2011-05-18 7:03 ` Tristan Gingold
2011-05-16 10:05 ` Marek Polacek
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='AANLkTikHGo+pgTGxBZq=-LZt-iVFr1Q9FywTuhPNbE_B@mail.gmail.com' \
--to=sedat.dilek@googlemail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gingold@adacore.com \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=sedat.dilek@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).