public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/54120] [4.8 Regression] FAIL: gfortran.fortran-torture/execute/random_2.f90 execution
Date: Tue, 31 Jul 2012 14:50:00 -0000 [thread overview]
Message-ID: <bug-54120-4-DmmgRwbI73@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54120-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54120
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
Component|fortran |middle-end
Target Milestone|--- |4.8.0
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-07-31 14:50:09 UTC ---
(In reply to comment #1)
> Introduced in 189366. Does this change affect recog_memoized?
That's the following commit:
Author: steven
Date: Mon Jul 9 08:45:12 2012
New Revision: 189366
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=189366
Log:
* gensupport.c (init_rtx_reader_args_cb): Start counting code
generating patterns from 1 to free up 0 for CODE_FOR_nothing.
* gencodes.c (main): Give CODE_FOR_nothing the value 0. Add
the LAST_INSN_CODE marker at the end.
* genoutput.c (nothing): New static struct data.
(idata): Initialize to ¬hing.
(idata_end): Initialize to ¬hing.next.
(init_insn_for_nothing): New function to create dummy 'nothing' insn.
(main): Use it.
* genpeep.c (insn_code_number): Remove global variable.
(gen_peephole): Take it as an argument instead.
(main): Take insn_code_number from read_md_rtx.
* optabs.h: Revert r161809:
(optab_handlers): Change type of insn_code back to insn_code.
(optab_handler, widening_optab_handler, set_optab_handler,
set_widening_optab_handler, convert_optab_handler,
set_convert_optab_handler, direct_optab_handler,
set_direct_optab_handler): Remove int casts.
Revert to treating the insn_code field as "insn_code".
Modified:
trunk/gcc/ChangeLog
trunk/gcc/gencodes.c
trunk/gcc/genoutput.c
trunk/gcc/genpeep.c
trunk/gcc/gensupport.c
trunk/gcc/optabs.h
next prev parent reply other threads:[~2012-07-31 14:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-29 17:46 [Bug fortran/54120] New: " danglin at gcc dot gnu.org
2012-07-30 20:55 ` [Bug fortran/54120] " danglin at gcc dot gnu.org
2012-07-31 14:50 ` burnus at gcc dot gnu.org [this message]
2012-09-19 14:08 ` [Bug middle-end/54120] " rguenth at gcc dot gnu.org
2012-12-19 10:55 ` jakub at gcc dot gnu.org
2012-12-19 12:58 ` dave.anglin at bell dot net
2012-12-22 23:01 ` danglin at gcc dot gnu.org
2012-12-22 23:02 ` danglin at gcc dot gnu.org
2012-12-22 23:07 ` jakub at gcc dot gnu.org
2012-12-22 23:35 ` danglin at gcc dot gnu.org
2012-12-22 23:38 ` danglin at gcc dot gnu.org
2013-01-07 14:51 ` jakub at gcc dot gnu.org
2013-01-07 16:34 ` jakub at gcc dot gnu.org
2013-01-07 17:28 ` jakub at gcc dot gnu.org
2013-01-07 18:09 ` dave.anglin at bell dot net
2013-01-08 8:34 ` jakub at gcc dot gnu.org
2013-01-08 9:09 ` 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-54120-4-DmmgRwbI73@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).