public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha 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: Tue, 10 Feb 2015 11:41:00 -0000 [thread overview]
Message-ID: <bug-64953-4-SdqVoTXD9i@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
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.
next prev parent reply other threads:[~2015-02-10 11:41 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 ` [Bug target/64953] " trippels at gcc dot gnu.org
2015-02-06 17:59 ` 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 [this message]
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-SdqVoTXD9i@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).