public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/55030] [4.8 Regression]: gcc.c-torture/execute/builtins/memcpy-chk.c execution,  -Os (et al)
Date: Tue, 27 Nov 2012 07:41:00 -0000	[thread overview]
Message-ID: <bug-55030-4-V8L9gaZz3h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55030-4@http.gcc.gnu.org/bugzilla/>


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

Andreas Krebbel <krebbel at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |krebbel at gcc dot gnu.org

--- Comment #7 from Andreas Krebbel <krebbel at gcc dot gnu.org> 2012-11-27 07:40:41 UTC ---
(In reply to comment #5)
> Author: hp
> Date: Mon Nov 26 03:22:15 2012
> New Revision: 193802
> 
> URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193802
> Log:
>     PR middle-end/55030
>     * builtins.c (expand_builtin_setjmp_receiver): Update comment
>     regarding purpose of blockage.
>     * emit-rtl.c [!HAVE_blockage] (gen_blockage): Similarly for
>     the head comment.
>     * rtlanal.c (volatile_insn_p): Ditto.
>     * doc/md.texi (blockage): Update similarly.  Change wording to
>     require one of two forms, rather than implying a wider choice.
>     * cse.c (cse_insn): Where checking for blocking insns, use
>     volatile_insn_p instead of manual check for volatile ASM.
>     * dse.c (scan_insn): Ditto.
>     * cselib.c (cselib_process_insn): Ditto.

This patch broke bootstrap on s390x.

/home/andreas/git/gcc-head/libgcc/libgcc2.c: In function ‘__powitf2’:
/home/andreas/git/gcc-head/libgcc/libgcc2.c:1779:1: internal compiler error: in
vt_expand_var_loc_chain, 
at var-tracking.c:8020
 }
 ^
0x80b9c219 vt_expand_var_loc_chain
        /home/andreas/git/gcc-head/gcc/var-tracking.c:8020
0x80b9cf23 vt_expand_loc_callback
        /home/andreas/git/gcc-head/gcc/var-tracking.c:8216
0x80305c7d cselib_expand_value_rtx_1
        /home/andreas/git/gcc-head/gcc/cselib.c:1683
0x80305e3b cselib_expand_value_rtx_1
        /home/andreas/git/gcc-head/gcc/cselib.c:1721
0x8030568d cselib_expand_value_rtx_cb(rtx_def*, bitmap_head_def*, int, rtx_def*
(*)(rtx_def*, bitmap_head
_def*, int, void*), void*)
        /home/andreas/git/gcc-head/gcc/cselib.c:1530
0x80b9c39b vt_expand_var_loc_chain
        /home/andreas/git/gcc-head/gcc/var-tracking.c:8054
0x80b9cf23 vt_expand_loc_callback
        /home/andreas/git/gcc-head/gcc/var-tracking.c:8216
0x80305c7d cselib_expand_value_rtx_1
        /home/andreas/git/gcc-head/gcc/cselib.c:1683
0x80305e3b cselib_expand_value_rtx_1
        /home/andreas/git/gcc-head/gcc/cselib.c:1721
0x8030568d cselib_expand_value_rtx_cb(rtx_def*, bitmap_head_def*, int, rtx_def*
(*)(rtx_def*, bitmap_head
_def*, int, void*), void*)
        /home/andreas/git/gcc-head/gcc/cselib.c:1530
0x80b9c39b vt_expand_var_loc_chain
        /home/andreas/git/gcc-head/gcc/var-tracking.c:8054
0x80b9cf23 vt_expand_loc_callback
        /home/andreas/git/gcc-head/gcc/var-tracking.c:8216
0x80305c7d cselib_expand_value_rtx_1
        /home/andreas/git/gcc-head/gcc/cselib.c:1683
0x8030568d cselib_expand_value_rtx_cb(rtx_def*, bitmap_head_def*, int, rtx_def*
(*)(rtx_def*, bitmap_head_def*, int, void*), void*)
        /home/andreas/git/gcc-head/gcc/cselib.c:1530
0x80b9c39b vt_expand_var_loc_chain
        /home/andreas/git/gcc-head/gcc/var-tracking.c:8054
0x80b9d67d vt_expand_1pvar
        /home/andreas/git/gcc-head/gcc/var-tracking.c:8331
0x80b9d9c7 emit_note_insn_var_location
        /home/andreas/git/gcc-head/gcc/var-tracking.c:8385
0x80f1a4e3 htab_traverse_noresize
        /home/andreas/git/gcc-head/libiberty/hashtab.c:784
0x80f1a5bf htab_traverse
        /home/andreas/git/gcc-head/libiberty/hashtab.c:800
0x80b9f613 emit_notes_for_changes
        /home/andreas/git/gcc-head/gcc/var-tracking.c:8749
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[5]: *** [_powitf2.o] Error 1
make[5]: *** Waiting for unfinished jobs....


  parent reply	other threads:[~2012-11-27  7:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23  0:58 [Bug middle-end/55030] New: " hp at gcc dot gnu.org
2012-10-23  1:05 ` [Bug middle-end/55030] " hp at gcc dot gnu.org
2012-10-23  1:08 ` hp at gcc dot gnu.org
2012-10-23  1:09 ` hp at gcc dot gnu.org
2012-10-23  9:39 ` rguenth at gcc dot gnu.org
2012-11-12  4:37 ` hp at gcc dot gnu.org
2012-11-12  4:54 ` hp at gcc dot gnu.org
2012-11-26  3:22 ` hp at gcc dot gnu.org
2012-11-26  3:26 ` hp at gcc dot gnu.org
2012-11-27  7:41 ` krebbel at gcc dot gnu.org [this message]
2012-11-27 11:55 ` hp at gcc dot gnu.org
2012-11-27 23:16 ` hp at gcc dot gnu.org
2013-02-16  9:37 ` ebotcazou at gcc dot gnu.org
2013-02-16  9:44 ` ebotcazou at gcc dot gnu.org
2013-02-17  0:33 ` hp at gcc dot gnu.org
2013-02-18 10:48 ` ebotcazou at gcc dot gnu.org
2013-02-18 22:21 ` hp at gcc dot gnu.org
2013-02-19 11:32 ` ebotcazou at gcc dot gnu.org
2013-06-03  8:37 ` mikpe at it dot uu.se
2013-06-03 22:32 ` hp at gcc dot gnu.org
2013-06-08  7:50 ` ebotcazou at gcc dot gnu.org
2013-07-03 14:44 ` hp 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-55030-4-V8L9gaZz3h@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).