public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/19266] [mudflap] ICE when compiling with -fmudflap -O
Date: Tue, 12 Apr 2005 18:09:00 -0000	[thread overview]
Message-ID: <20050412180916.3410.qmail@sourceware.org> (raw)
In-Reply-To: <20050105154223.19266.martin@mpa-garching.mpg.de>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-04-12 18:09 -------
Subject: Bug 19266

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	fche@gcc.gnu.org	2005-04-12 18:09:09

Modified files:
	gcc            : ChangeLog tree-mudflap.c 
	libmudflap     : ChangeLog 
	libmudflap/testsuite/libmudflap.c++: c++frags.exp 
Added files:
	libmudflap/testsuite/libmudflap.c++: pass57-frag.cxx 

Log message:
	2005-04-12  Frank Ch. Eigler  <fche@redhat.com>
	
	PR mudflap/19266
	From Richard Henderson <rth@redhat.com>:
	* tree-mudflap.c (mf_build_check_statement_for): Correct block
	splitting logic.
	
	2005-04-12  Frank Ch. Eigler  <fche@redhat.com>
	
	PR mudflap/19266
	* testsuite/libmudflap.c++/c++frags.exp: Also test -O permutation.
	* testsuite/libmudflap.c++/pass57-frag.cxx: New test.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.8251&r2=2.8252
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-mudflap.c.diff?cvsroot=gcc&r1=2.36&r2=2.37
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libmudflap/ChangeLog.diff?cvsroot=gcc&r1=1.54&r2=1.55
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libmudflap/testsuite/libmudflap.c++/pass57-frag.cxx.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libmudflap/testsuite/libmudflap.c++/c++frags.exp.diff?cvsroot=gcc&r1=1.5&r2=1.6



-- 


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


  parent reply	other threads:[~2005-04-12 18:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 15:43 [Bug other/19266] New: " martin at mpa-garching dot mpg dot de
2005-01-05 15:44 ` [Bug other/19266] " martin at mpa-garching dot mpg dot de
2005-01-05 15:46 ` martin at mpa-garching dot mpg dot de
2005-01-05 15:51 ` pinskia at gcc dot gnu dot org
2005-01-05 15:51 ` pinskia at gcc dot gnu dot org
2005-01-05 19:41 ` pinskia at gcc dot gnu dot org
2005-01-05 19:45 ` martin at mpa-garching dot mpg dot de
2005-01-05 20:36 ` pinskia at gcc dot gnu dot org
2005-01-06  2:50 ` fche at redhat dot com
2005-04-08 13:51 ` pinskia at gcc dot gnu dot org
2005-04-12 16:50 ` fche at redhat dot com
2005-04-12 18:09 ` cvs-commit at gcc dot gnu dot org [this message]
2005-04-12 18:10 ` fche at redhat dot com
2005-06-15  3:29 ` pinskia at gcc dot gnu dot org
2005-06-23 11:35 ` reichelt at gcc dot gnu dot org
2005-08-15 14:12 ` pinskia at gcc dot gnu dot org
2005-08-24 11:54 ` pinskia at gcc dot gnu dot org
     [not found] <bug-19266-2736@http.gcc.gnu.org/bugzilla/>
2005-11-16 21:20 ` pinskia at gcc dot gnu dot org
2005-12-06 22:38 ` pinskia at gcc dot gnu dot org
2006-01-24 15:50 ` pinskia at gcc dot gnu dot 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=20050412180916.3410.qmail@sourceware.org \
    --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).