public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Richard Guenther" <richard.guenther@gmail.com>
To: "Aldy Hernandez" <aldyh@redhat.com>
Cc: gcc-patches@gcc.gnu.org, stevenb.gcc@gmail.com, bonzini@gnu.org,
	 	rguenther@suse.de, matz@suse.de
Subject: Re: PR33713: remove -fforce-addr
Date: Fri, 30 Nov 2007 00:28:00 -0000	[thread overview]
Message-ID: <84fc9c000711291333w582d056eo9f379ec8a4797de4@mail.gmail.com> (raw)
In-Reply-To: <20071129175051.GA12296@redhat.com>

On Nov 29, 2007 6:50 PM, Aldy Hernandez <aldyh@redhat.com> wrote:
> Hi folks.
>
> I'm picking up this patch that Steven attached to the PR but didn't
> submit to the list.  The patch removes support for -fforce-addr.
>
>         http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33713
>
> I have added a changelog, incorporated the change suggested by Paolo,
> fixed a typo, and tested it on x86_64-linux.  There are no regressions.
>
> Is this OK for mainline?

This is ok.  But please also provide an entry for the 4.3 changes.html page.

Thanks,
Richard.

>         PR33713
>         * doc/invoke.texi: Remove -fforce-addr documentation.
>         * expr.c (emit_move_insn): Remove use of flag_force_addr.
>         (expand_expr_real_1): Same.
>         (do_tablejump): Same.
>         Call memory_address instead of memory_address_noforce.
>         * expr.h (memory_address_noforce): Remove prototype.
>         * explow.c (memory_address): Remove support for flag_force_addr.
>         (validize_mem): Same.
>         (memory_address_noforce): Remove.
>         * common.opt: Add dummy documentation for -fforce-addr.
>         * combine.c (can_combine_p): Remove -fforce-addr comment.
>         * config/cris/cris.h: Update CC1_SPEC comment with regards to
>         -fforce-addr.
>         (OPTIMIZATION_OPTIONS): Remove set of flag_force_addr.
>         * config/m68k/m68k.h (PIC_CASE_VECTOR_ADDRESS): Remove comment
>         relating to memory_address_noforce.
>
>         * gcc.c-torture/compile/20050802-1.c: Remove.
>         * gcc.c-torture/compile/20011113-1.c: Remove.

  reply	other threads:[~2007-11-29 21:35 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 [this message]
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
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=84fc9c000711291333w582d056eo9f379ec8a4797de4@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=aldyh@redhat.com \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=matz@suse.de \
    --cc=rguenther@suse.de \
    --cc=stevenb.gcc@gmail.com \
    /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).