public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reed.kotler at imgtec dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60556] tip of tree crash with mips compiler
Date: Mon, 17 Mar 2014 23:54:00 -0000	[thread overview]
Message-ID: <bug-60556-4-rbWZf00tey@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60556-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60556

--- Comment #12 from reed kotler <reed.kotler at imgtec dot com> ---
(In reply to Andrew Pinski from comment #11)
> (In reply to Andrew Pinski from comment #10)
> > I should note the code is undefined and has (uint64_t)&stat and that itself
> > is causing the issue.  If I change it to be
> > (uint64_t)(unsigned long)&stat, GCC does not crash.
> 
> But using long instead of unsigned long causes the crash.
> 
> Reduced testcase:
> int g (int);
> unsigned long long f(void) {
>  return (unsigned long long)(long)&g;
> }
> 
> This happens with both the C and C++ front-ends.

Thanks.

Do you know where the original line was that made it fail in the .ii?

Depending on the location, I can possibly make the source change for now until
the bug gets fixed in gcc.


  parent reply	other threads:[~2014-03-17 23:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 20:45 [Bug c++/60556] New: " reed.kotler at imgtec dot com
2014-03-17 20:46 ` [Bug c++/60556] " reed.kotler at imgtec dot com
2014-03-17 21:04 ` [Bug target/60556] " pinskia at gcc dot gnu.org
2014-03-17 21:08 ` pinskia at gcc dot gnu.org
2014-03-17 21:09 ` reed.kotler at imgtec dot com
2014-03-17 21:17 ` pinskia at gcc dot gnu.org
2014-03-17 21:23 ` reed.kotler at imgtec dot com
2014-03-17 21:25 ` reed.kotler at imgtec dot com
2014-03-17 21:32 ` pinskia at gcc dot gnu.org
2014-03-17 21:33 ` reed.kotler at imgtec dot com
2014-03-17 22:05 ` pinskia at gcc dot gnu.org
2014-03-17 22:16 ` pinskia at gcc dot gnu.org
2014-03-17 23:54 ` reed.kotler at imgtec dot com [this message]
2014-03-18  0:14 ` pinskia at gcc dot gnu.org
2014-03-19 16:36 ` reed.kotler at imgtec dot com
2014-03-19 17:45 ` sje at gcc dot gnu.org
2014-03-20 16:27 ` [Bug middle-end/60556] " sje at gcc dot gnu.org
2014-04-11 11:52 ` jakub at gcc dot gnu.org
2014-04-11 11:58 ` jakub 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-60556-4-rbWZf00tey@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).