public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: PR33713: remove -fforce-addr
Date: Fri, 07 Dec 2007 16:18:00 -0000	[thread overview]
Message-ID: <20071207161821.GY17368@sygehus.dk> (raw)
In-Reply-To: <20071129175051.GA12296@redhat.com>

On Thu, Nov 29, 2007 at 01:50:51PM -0400, Aldy Hernandez wrote:

> Index: explow.c
> ===================================================================
> --- explow.c	(revision 130511)
> +++ explow.c	(working copy)
[...]
> @@ -482,17 +485,6 @@ memory_address (enum machine_mode mode, 
>  	 the register is a valid address.  */
>        else
>  	x = force_reg (Pmode, x);
> -
> -      goto done;
> -
> -    win2:
> -      x = oldx;
> -    win:
> -      if (flag_force_addr && ! cse_not_expected && !REG_P (x))
> -	{
> -	  x = force_operand (x, NULL_RTX);
> -	  x = force_reg (Pmode, x);
> -	}
>      }
>  
>   done:

   This breaks at least m32c-unknown-elf:

make[2]: Entering directory `/home/rask/build/gcc-m32c-unknown-elf/gcc'
gcc -c   -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wmissing-format-attribute -fno-common   -DHAVE_CONFIG_H -I. -I. -I/home/rask/src/all/gcc -I/home/rask/src/all/gcc/. -I/home/rask/src/all/gcc/../include -I/home/rask/src/all/gcc/../libcpp/include  -I/home/rask/src/all/gcc/../libdecnumber -I/home/rask/src/all/gcc/../libdecnumber/dpd -I../libdecnumber    /home/rask/src/all/gcc/explow.c -o explow.o
/home/rask/src/all/gcc/explow.c: In function memory_address:
/home/rask/src/all/gcc/explow.c:448: error: label win used but not defined
make[2]: *** [explow.o] Error 1

-- 
Rask Ingemann Lambertsen
Danish law requires addresses in e-mail to be logged and stored for a year

  parent reply	other threads:[~2007-12-07 16:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 21:35 Aldy Hernandez
2007-11-30  0:28 ` Richard Guenther
2007-12-03 23:18   ` PR33713: remove -fforce-addr (changes.html patch) Aldy Hernandez
2007-12-03 23:29     ` Gerald Pfeifer
2007-11-30  8:09 ` PR33713: remove -fforce-addr Michael Meissner
2007-11-30 11:49   ` Paolo Bonzini
2007-11-30 12:52   ` Steven Bosscher
2007-11-30 15:05   ` Richard Guenther
2007-11-30 18:17     ` Steven Bosscher
2007-12-03 23:11       ` Aldy Hernandez
2007-12-02 11:31 ` Hans-Peter Nilsson
     [not found] ` <200712041513.lB4FDJle014800@ignucius.se.axis.com>
2007-12-04 15:19   ` Aldy Hernandez
2007-12-04 22:53     ` Hans-Peter Nilsson
2007-12-04 23:13       ` Aldy Hernandez
2007-12-14  2:06         ` Hans-Peter Nilsson
2007-12-14  7:59           ` Steven Bosscher
2007-12-14 12:02             ` Hans-Peter Nilsson
2007-12-14 13:32               ` Steven Bosscher
2007-12-07 16:18 ` Rask Ingemann Lambertsen [this message]
2007-12-07 16:48   ` Aldy Hernandez
2007-12-07 17:14     ` DJ Delorie
2007-12-07 17:17     ` Rask Ingemann Lambertsen

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=20071207161821.GY17368@sygehus.dk \
    --to=rask@sygehus.dk \
    --cc=aldyh@redhat.com \
    --cc=gcc-patches@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).