public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001154] HAL_DISABLE_INTERRUPTS miscompile on Cortex-M3
Date: Thu, 17 Feb 2011 13:43:00 -0000 [thread overview]
Message-ID: <20110217134312.CCB532FB0004@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001154-13@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001154
John Dallaway <john@dallaway.org.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
AssignedTo|unassigned@bugs.ecos.source |john@dallaway.org.uk
|ware.org |
Ever Confirmed|0 |1
--- Comment #4 from John Dallaway <john@dallaway.org.uk> 2011-02-17 13:43:10 GMT ---
Created an attachment (id=1133)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1133)
cortexm-intr-110217.patch
This patch marks the HAL_DISABLE_INTERRUPTS() operand as an earlyclobber
operand.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-02-17 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 14:30 [Bug 1001154] New: " bugzilla-daemon
2011-02-16 14:59 ` [Bug 1001154] " bugzilla-daemon
2011-02-16 15:09 ` bugzilla-daemon
2011-02-16 15:18 ` bugzilla-daemon
2011-02-17 13:43 ` bugzilla-daemon [this message]
2011-02-17 13:44 ` bugzilla-daemon
2011-03-04 13:06 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2011-02-16 14:30 [Bug 1001154] New: " bugzilla-daemon
2011-02-16 14:59 ` [Bug 1001154] " bugzilla-daemon
2011-02-16 15:09 ` bugzilla-daemon
2011-02-16 15:18 ` bugzilla-daemon
2011-02-17 13:43 ` bugzilla-daemon
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=20110217134312.CCB532FB0004@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-bugs@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).