public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001520] Fix compiler warnings in Cortex-M architecture HAL Date: Sun, 11 Mar 2012 23:22:00 -0000 [thread overview] Message-ID: <20120311232222.A42F63F70006@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001520-777@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=1001520 Jonathan Larmour <jifl@ecoscentric.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jifl@ecoscentric.com AssignedTo|unassigned@bugs.ecos.source |jifl@ecoscentric.com |ware.org | --- Comment #1 from Jonathan Larmour <jifl@ecoscentric.com> 2012-03-11 23:22:21 GMT --- I would like to be very sure that GCC 4.6 is not going to try and optimise away the read. Can you provide a disassembly of something containing that macro, compiled with -O2 ? I don't have a suitable GCC 4.6 available to me here. Thanks, Jifl -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next prev parent reply other threads:[~2012-03-11 23:22 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-07 14:35 [Bug 1001520] New: " bugzilla-daemon 2012-03-11 23:22 ` bugzilla-daemon [this message] 2012-03-07 14:35 bugzilla-daemon 2012-03-11 23:22 ` [Bug 1001520] " bugzilla-daemon 2012-03-12 9:18 ` bugzilla-daemon 2012-03-12 14:56 ` bugzilla-daemon 2012-03-12 14:56 ` bugzilla-daemon 2012-03-12 16:26 ` bugzilla-daemon 2012-03-12 19:11 ` 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=20120311232222.A42F63F70006@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@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: linkBe 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).