public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64953] Compiling sourcecode for STM32F103 causes USB errors with some optimization settings
Date: Thu, 05 Feb 2015 19:44:00 -0000 [thread overview]
Message-ID: <bug-64953-4-013oPHLve9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64953-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64953
Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |trippels at gcc dot gnu.org
--- Comment #2 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to manuel.reimer from comment #0)
> After some trying I've found out that the key in this case is the
> optimization setting. If I use "-O3", then the resulting binary works again
> if I use the 4.9.2 compiler.
>
> So "something" is wrong with the optimization.
>
> Can someone give me a hint about what changed between 4.8 and 4.9.2? Is this
> a bug in the gcc compiler or do I just need some new "compiler switch" to
> disable "some new feature" and get a valid binary, again?
Try to narrow the issue down to a single source file. Once you have found
the file in question, you may narrow the problem down to a single function
by using __attribute__((optimize("-Os"))).
You could also try to build the application with -fsanitize=undefined
and see if any issue pops up.
next prev parent reply other threads:[~2015-02-05 19:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 19:30 [Bug c/64953] New: " manuel.reimer at gmx dot de
2015-02-05 19:34 ` [Bug c/64953] " manuel.reimer at gmx dot de
2015-02-05 19:44 ` trippels at gcc dot gnu.org [this message]
2015-02-06 17:59 ` [Bug target/64953] " manuel.reimer at gmx dot de
2015-02-06 18:23 ` trippels at gcc dot gnu.org
2015-02-06 18:27 ` manuel.reimer at gmx dot de
2015-02-06 18:28 ` manuel.reimer at gmx dot de
2015-02-08 21:23 ` manuel.reimer at gmx dot de
2015-02-08 21:33 ` trippels at gcc dot gnu.org
2015-02-08 21:45 ` manuel.reimer at gmx dot de
2015-02-09 5:51 ` trippels at gcc dot gnu.org
2015-02-10 11:41 ` rearnsha at gcc dot gnu.org
2015-02-10 16:17 ` manuel.reimer at gmx dot de
2015-02-10 16:52 ` rearnsha at gcc dot gnu.org
2015-02-10 17:17 ` manuel.reimer at gmx dot de
2015-02-10 17:23 ` manuel.reimer at gmx dot de
2015-02-10 18:38 ` pinskia at gcc dot gnu.org
2015-02-10 19:44 ` manuel.reimer at gmx dot de
2015-02-13 8:34 ` maltsevm at gmail dot com
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=bug-64953-4-013oPHLve9@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).