public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manuel.reimer at gmx dot de" <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 17:23:00 -0000 [thread overview] Message-ID: <bug-64953-4-lxf08sJJ2X@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 manuel.reimer at gmx dot de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #15 from manuel.reimer at gmx dot de --- This is what "git bisect" ended with. Maybe someone can at least have a look at this. Feel free to close again if this really doesn't help at all. $ git bisect bad9eec20bfd5806dd0380e07dbc0f03409ce3d4efb is the first bad commit commit 9eec20bfd5806dd0380e07dbc0f03409ce3d4efb Author: rguenth <rguenth@138bc75d-0d04-0410-961f-82ee72b054a4> Date: Tue Mar 26 09:14:59 2013 +0000 2013-03-26 Richard Biener <rguenther@suse.de> * emit-rtl.c (set_mem_attributes_minus_bitpos): Remove alignment computations and rely on get_object_alignment_1 for the !TYPE_P case. Commonize DECL/COMPONENT_REF handling in the ARRAY_REF path. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@197095 138bc75d-0d04-0410-961f-82ee72b054a4 :040000 040000 f4fa27b8adaec983566fb9cb72d1165d10c86048 a13a68729d60b22dd6c45edb3ef7c3c52b3a2f41 M gcc
next prev parent reply other threads:[~2015-02-10 17:23 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 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 [this message] 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-lxf08sJJ2X@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: 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).