public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gccbugzilla@tru-traffic.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/56716] during gcc 4.8.0 build on Cygwin:  bid128_fma.c:4460:1: internal compiler error: Segmentation fault
Date: Wed, 24 Apr 2013 23:53:00 -0000	[thread overview]
Message-ID: <bug-56716-4-wA9TDWZqHy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56716-4@http.gcc.gnu.org/bugzilla/>


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

Greg <gccbugzilla@tru-traffic.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gccbugzilla@tru-traffic.com

--- Comment #4 from Greg <gccbugzilla@tru-traffic.com> 2013-04-24 23:53:15 UTC ---
(In reply to comment #3)
> Author: rguenth
> Date: Wed Mar 27 15:10:50 2013
> New Revision: 197165
> 
> URL: http://gcc.gnu.org/viewcvs?rev=197165&root=gcc&view=rev
> Log:
> 2013-03-27  Richard Biener  <rguenther@suse.de>
> 
>     PR tree-optimization/56716
>     * tree-ssa-structalias.c (perform_var_substitution): Adjust
>     dumping for ref nodes.
> 
> Modified:
>     trunk/gcc/ChangeLog
>     trunk/gcc/tree-ssa-structalias.c
> 
> Fixed the issue on trunk.  Back to analysis.

I get the same error, and merging revision 197165 from trunk into my
working-directory for gcc-4_8-branch revision 198253 did not fix the error on
my system.

This error occured during one of the stages while building gcc, revision
198065, checked out from svn://gcc.gnu.org/svn/gcc/branches/gcc-4_8-branch for
MinGW32, Windows 7 Pro 64-bit SP1.
The error also occurs with revisions 198027 and 198253 -- that is, the error
has been occuring with revisions for at least these past 7 days.

The error persists after I merged revision 197165 from trunk into my
working-directory for gcc-4_8-branch revision 198253.


  parent reply	other threads:[~2013-04-24 23:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  1:35 [Bug c/56716] New: " pen7cmc at yahoo dot com
2013-03-25  1:37 ` [Bug c/56716] " pen7cmc at yahoo dot com
2013-03-27 12:43 ` [Bug target/56716] " aldot at gcc dot gnu.org
2013-03-27 13:46 ` rguenth at gcc dot gnu.org
2013-03-27 15:12 ` rguenth at gcc dot gnu.org
2013-04-24 23:53 ` gccbugzilla@tru-traffic.com [this message]
2013-04-25  8:06 ` rguenth at gcc dot gnu.org
2013-04-25 22:32 ` gccbugzilla@tru-traffic.com
2013-04-27 16:16 ` gccbugzilla@tru-traffic.com
2013-04-27 21:54 ` gccbugzilla@tru-traffic.com
2013-04-27 22:35 ` aldot at gcc dot gnu.org
2013-04-27 23:28 ` gccbugzilla@tru-traffic.com
2013-09-27 16:44 ` pmatos at gcc dot gnu.org
2013-12-16  9:49 ` ktietz 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-56716-4-wA9TDWZqHy@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).