This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/64953] Compiling sourcecode for STM32F103 causes USB errors with some optimization settings
- From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 10 Feb 2015 11:40:59 +0000
- Subject: [Bug target/64953] Compiling sourcecode for STM32F103 causes USB errors with some optimization settings
- Auto-submitted: auto-generated
- References: <bug-64953-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64953
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2015-02-10
Ever confirmed|0 |1
--- Comment #11 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to manuel.reimer from comment #0)
> So "something" is wrong with the optimization.
Not necessarily. Your program may have a bug in it: many bugs are only shown
up by higher levels of optimization.
We don't have your hardware and we don't have the full code to your
application, so we aren't going to be able to help you debug this.
To take this any further you'll need to show us why you think the compiler has
mis-optimized your code. I think that's a more useful approach than trying to
identify the change in GCC that causes the code to fail.