public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: gcc@ds217-115-141-84.dedicated.hosteurope.de
To: gcc@gcc.gnu.org
Subject: new FAILs on HEAD
Date: Thu, 31 Jul 2003 09:33:00 -0000	[thread overview]
Message-ID: <200307310720.h6V7K0xB004534@ds217-115-141-84.dedicated.hosteurope.de.> (raw)

These new FAILs

FAIL: g++.old-deja/g++.other/crash18.C (test for excess errors)
FAIL: gcc.misc-tests/mg.c

were caused by one of the following checkins

2003-07-31  Ulrich Weigand  <uweigand@de.ibm.com>

	* config/s390/s390.md (UNSPEC_ROUND, UNSPEC_SETHIGH, 
	UNSPECV_BLOCKAGE): New constants.
	("*sethighqisi", "*sethighhisi", "*sethiqidi_64", "*sethiqidi_31",
	"*extractqi", "*extracthi", "*extendqidi2" splitter, "*extendqisi2"
	splitter, "fix_truncdfdi2_ieee", "fix_truncdfsi2_ieee",
	"fix_truncsfdi2", "fix_truncsfsi2", "blockage"): Use them.

	(all insns and expanders): Write output control string as brace block
	where appropriate.  Remove \-escapes for doublequote characters.

Thu Jul 31 01:04:19 CEST 2003  Jan Hubicka  <jh@suse.cz>

	* gcse.c (insert_store): Fix typo in previous patch.

2003-07-29  Andrew Pinski <pinskia@physics.uc.edu>

	PR target/11565
	* gcc.dg/i386-387-1.c (dg-options): Add -march=i386.
	* gcc.dg/i386-387-5.c (dg-options): Likewise.


debian GNU/Linux i686 unstable

             reply	other threads:[~2003-07-31  7:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31  9:33 gcc [this message]
2003-07-31 10:31 gcc
     [not found] <20031224055000.A1860@ds217-115-141-84>
2003-12-24 11:14 ` Zack Weinberg
2003-12-24 11:15   ` Daniel Jacobowitz
2003-12-24 11:16     ` Zack Weinberg
2003-12-25  0:38       ` Laurent GUERBY
2004-08-15  3:49 Michael Ritzert
2004-08-15 10:20 ` Joseph S. Myers

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=200307310720.h6V7K0xB004534@ds217-115-141-84.dedicated.hosteurope.de. \
    --to=gcc@ds217-115-141-84.dedicated.hosteurope.de \
    --cc=gcc@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).