public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/48333] -fcompare-debug failure (length) - "memmove" x "__builtin_memmove" Date: Thu, 31 Mar 2011 07:53:00 -0000 [thread overview] Message-ID: <bug-48333-4-j9I96d1ejB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48333-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48333 --- Comment #3 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2011-03-31 06:12:22 UTC --- Created attachment 23832 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23832 Patch that fixes the bug It's a garbage collection issue: we're supposed to share mem_attrs involving __builtin and non-__builtin functions, and we do, unless GC manages to discard mem_attrs at precisely the worst possible moment, and does so at only one of the compilations, and we're unlucky to end up inserting a different one next time it is required. A more general solution would amount to checking for builtins at dump time, and discarding the __builtin prefix or noting it as optional or somesuch, but I'm testing this simpler and hopefully effective solution instead.
next prev parent reply other threads:[~2011-03-31 6:12 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-29 13:10 [Bug debug/48333] New: " zsojka at seznam dot cz 2011-03-30 8:42 ` [Bug debug/48333] " rguenth at gcc dot gnu.org 2011-03-30 22:40 ` aoliva at gcc dot gnu.org 2011-03-31 7:53 ` aoliva at gcc dot gnu.org [this message] 2011-05-19 11:07 ` jakub at gcc dot gnu.org 2011-06-04 10:09 ` aoliva at gcc dot gnu.org 2011-06-04 10:18 ` aoliva at gcc dot gnu.org
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-48333-4-j9I96d1ejB@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).