public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: H.J. Lu <hjl.tools@gmail.com>
Cc: sedat.dilek@gmail.com, binutils <binutils@sourceware.org>,
	Alan Modra <amodra@gmail.com>
Subject: Re: Release 2.21.1 ?
Date: Wed, 16 Mar 2011 12:47:00 -0000	[thread overview]
Message-ID: <5747FA00-EAB3-45A2-A4D9-05F8642076D7@adacore.com> (raw)
In-Reply-To: <AANLkTim=SUneXWN5uPSwXJE_Hp0KotMxx=ZyVtq17+Vp@mail.gmail.com>


On Mar 16, 2011, at 1:44 PM, H.J. Lu wrote:

> On Wed, Mar 16, 2011 at 5:16 AM, Alan Modra <amodra@gmail.com> wrote:
>> On Wed, Mar 16, 2011 at 09:50:35AM +0100, Tristan Gingold 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 ?
>> 
>> Well, it's plain wrong to accept bad expressions and have gas try to
>> guess what typos mean, so I think it should be an error.  The size
>> info matters to some people.  Ask gdb developers, or anyone writing
>> code analysis and optimization tools.
>> 
>> I also think it highly likely that new binutils and/or gcc will break
>> kernel bisection in other areas.  For that reason I'm inclined to
>> discount the kernel list histrionics over the .size fix.  Kernel
>> kiddies are just going to have to learn to deal with toolchain
>> evolution.
>> 
> 
> Can I apply my size error patch?

Sure.

  reply	other threads:[~2011-03-16 12:47 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
2011-03-16 12:17   ` Alan Modra
2011-03-16 12:44     ` H.J. Lu
2011-03-16 12:47       ` Tristan Gingold [this message]
  -- 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=5747FA00-EAB3-45A2-A4D9-05F8642076D7@adacore.com \
    --to=gingold@adacore.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.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).