From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001528] compat/posix: porting to GCC 4.6
Date: Tue, 13 Mar 2012 14:27:00 -0000 [thread overview]
Message-ID: <20120313142652.6916B2F78001@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001528-104@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=1001528
--- Comment #4 from Jonathan Larmour <jifl@ecoscentric.com> 2012-03-13 14:26:50 GMT ---
Thanks for the disassembly.
(In reply to comment #3)
>
> Thus, new compiler uses less registers, but, GCC 4.6 provides the same
> functionality (I tested the loop in GDB, and I got `sigbus' call at the
> end with new code). Though, you are right, a using CYGBLD_ATTRIB_UNUSED
> for the forced volatile variables would break smart things.
Well, it _could_ break things if the gcc policy was that even volatile accesses
could be eliminated for things which are both unused and explicitly marked
unused. That appears not to be the case, which is good.
> Then, maybe leave signal2 test without the changes as I tested the code
> for one CPU only? What is your verdict?
No it can go. If GCC thought it was unused and could be discarded it would
definitely get rid of it during optimisation, and that would be true on all
architectures.
So your full patch including signal2 change can go in now, thanks!
Jifl
--
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:[~2012-03-13 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 20:27 [Bug 1001528] New: " bugzilla-daemon
2012-03-11 23:19 ` [Bug 1001528] " bugzilla-daemon
2012-03-12 17:36 ` bugzilla-daemon
2012-03-13 12:34 ` bugzilla-daemon
2012-03-13 14:27 ` bugzilla-daemon [this message]
2012-03-13 14:54 ` 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=20120313142652.6916B2F78001@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@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).