public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/56546] Using the divide operator on unsigned int produces incorrect code on AVR Date: Mon, 11 Mar 2013 11:50:00 -0000 [thread overview] Message-ID: <bug-56546-4-FXrN6ZXiNl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56546-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56546 Georg-Johann Lay <gjl at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID --- Comment #3 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2013-03-11 11:50:02 UTC --- (In reply to comment #2) > (In reply to comment #1) >> Is this an unpatched avr-gcc? > > In fact I discovered the issue on a toolchain built with Gentoo's crossdev > tool. They are using a good number of patches but these are not the source of > the problem. After digging a little deeper I discovered that the problem comes > from the build options they use. After a good number of builds on an unpatched > gcc-4.7.2 I've been able to determine that the --disable-multilib option they > use is the source of the issue. --disable-multilib completely messes up the tools, thus closing this PR as INVALID. > Building with > > ../configure [...] Notice that configuring in the source tree is strongly discouraged / not supported. Read the configuring GCC documentation again. If you are using AVR-LibC, you may also want to configure with --with-avrlibc=yes and use AVR-LibC that implements http://savannah.nongnu.org/bugs/?35407
prev parent reply other threads:[~2013-03-11 11:50 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-05 22:12 [Bug target/56546] New: " kpet at free dot fr 2013-03-07 22:21 ` [Bug target/56546] " gjl at gcc dot gnu.org 2013-03-10 17:24 ` kpet at free dot fr 2013-03-11 11:50 ` gjl at gcc dot gnu.org [this message]
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-56546-4-FXrN6ZXiNl@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).