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: "trippels at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 09 Feb 2015 05:50:54 +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
--- Comment #10 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to manuel.reimer from comment #9)
> The two commits are in different branches. How to bisect in this case?
gcc's history is linear in git. So you could start with a
bad commit on 20140302 and go back a year and use e.g. a commit on
20130302 as good.
(Or you could wait until an ARM guy takes a look at this bug...)