From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: Bisected: RED State Exception in 4.5 on E420R
Date: Thu, 28 Apr 2016 20:57:15 +0000 [thread overview]
Message-ID: <20160428205714.GA30251@ravnborg.org> (raw)
In-Reply-To: <alpine.LRH.2.20.1604061729350.16827@math.ut.ee>
>
> Do you know exactly when plain "ASSERT()" starts working and doesn't
> require the ". = " part?
I have digged a little. The original bug report is here:
http://marc.info/?l=linux-kbuild&m\x124930110427870&w=2
Here Jean report that is fails with binutils 2.14, and
Documentation/Changes list 2.12 as the minimum required version.
The bug will only manifest itself with a "plain" ASSERT.
So ASSERT placed inside:
SECTIONS
{
.text TEXTSTART:
{
}
ASSERT(bla bla, bla);
}
Will to my best understanding not trigger the bug.
x86 has a similar assert in line 186.
I did not test it - getting late here.
Will try to go through the .S files tomorrow to check
if I can find additional places where we can save
a few bytes.
And I may try to implment the above too.
Sam
next prev parent reply other threads:[~2016-04-28 20:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 8:22 Bisected: RED State Exception in 4.5 on E420R Meelis Roos
2016-04-11 3:45 ` David Miller
2016-04-27 13:21 ` Meelis Roos
2016-04-27 19:33 ` David Miller
2016-04-27 19:36 ` David Miller
2016-04-27 19:46 ` Rob Gardner
2016-04-27 19:55 ` Meelis Roos
2016-04-27 20:01 ` David Miller
2016-04-27 20:02 ` David Miller
2016-04-27 20:06 ` Rob Gardner
2016-04-27 20:22 ` David Miller
2016-04-27 20:49 ` Sam Ravnborg
2016-04-27 20:52 ` David Miller
2016-04-27 20:53 ` David Miller
2016-04-28 4:58 ` Joerg Abraham
2016-04-28 17:26 ` mroos
2016-04-28 17:38 ` David Miller
2016-04-28 19:49 ` Sam Ravnborg
2016-04-28 20:10 ` David Miller
2016-04-28 20:57 ` Sam Ravnborg [this message]
2016-04-28 22:54 ` Rob Gardner
2016-04-29 0:16 ` Julian Calaby
2016-05-01 23:36 ` David Miller
2016-05-01 23:41 ` David Miller
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=20160428205714.GA30251@ravnborg.org \
--to=sam@ravnborg.org \
--cc=sparclinux@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.