public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gary at intrepid dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/27445] create_tmp_var_raw (gimplify.c) inadventently asserts 'volatile' on temps Date: Sat, 06 May 2006 01:42:00 -0000 [thread overview] Message-ID: <20060506014207.18927.qmail@sourceware.org> (raw) In-Reply-To: <bug-27445-9975@http.gcc.gnu.org/bugzilla/> ------- Comment #12 from gary at intrepid dot com 2006-05-06 01:42 ------- Given the above, I suggest that my bug report be marked closed, because the problem I was seeing in 4.0.1 is fixed by the change to create_tmp_from_val that passes in TYPE_MAIN_VARIANT(). Note that the use of the main variant is stronger (removes more qualifiers/attirbutes) than the code that sets new_type anyway. It might be a good idea to remove the setting of new_type since it isn't used. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27445
prev parent reply other threads:[~2006-05-06 1:42 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-05 16:02 [Bug c/27445] New: " gary at intrepid dot com 2006-05-05 16:05 ` [Bug c/27445] " pinskia at gcc dot gnu dot org 2006-05-05 16:06 ` gary at intrepid dot com 2006-05-05 16:12 ` gary at intrepid dot com 2006-05-05 16:16 ` [Bug middle-end/27445] " pinskia at gcc dot gnu dot org 2006-05-05 16:37 ` gary at intrepid dot com 2006-05-05 16:39 ` Andrew Pinski 2006-05-05 16:39 ` pinskia at physics dot uc dot edu 2006-05-05 16:58 ` gary at intrepid dot com 2006-05-05 17:10 ` pinskia at gcc dot gnu dot org 2006-05-05 17:55 ` gary at intrepid dot com 2006-05-05 18:06 ` Daniel Berlin 2006-05-05 18:07 ` dberlin at dberlin dot org 2006-05-06 1:17 ` rth at gcc dot gnu dot org 2006-05-06 1:42 ` gary at intrepid dot com [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=20060506014207.18927.qmail@sourceware.org \ --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).