From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: ramrad01@arm.com, gcc-patches@gcc.gnu.org, rdsandiford@googlemail.com
Subject: Re: [0/8] Add optabs alternatives for insv, extv and extzv
Date: Tue, 27 Nov 2012 22:45:00 -0000 [thread overview]
Message-ID: <CAJA7tRYbJROUR5HAHhoLRu73+8Jr5ocj3mR3CLxiTZRJLuzNBg@mail.gmail.com> (raw)
In-Reply-To: <878v9mdcdl.fsf@talisman.default>
On Tue, Nov 27, 2012 at 8:22 PM, Richard Sandiford
<rdsandiford@googlemail.com> wrote:
> Ramana Radhakrishnan <ramrad01@arm.com> writes:
>>> Tested on x86_64-linux-gnu, powerpc64-linux-gnu and mipsisa64-elf.
>>> Also tested by making sure that there were no changes in assembly
>>> output for a set of gcc .ii files. On the other hand, the -march=octeon
>>> output for a set of mips64-linux-gnu gcc .ii files showed the optimisation
>>> kicking in as hoped.
>>
>> This sequence of patches caused a regression in
>> gcc.target/arm/volatile-bitfields-1.c . I haven't reviewed the patch
>> stack in great detail yet, but it looks like this sequence of patches
>> doesn't take the ARM volatile bitfields into account. (193600 is fine,
>> 193606 is not).
>
> Looks like I was wrong to drop the conditions from patch 5.
> Please could you try the attached?
Fixes volatile-bitfields-1.c but appears to break volatile-bitfields-4.c :( .
Ramana
>
> Richard
>
>
> gcc/
> * expmed.c (adjust_bit_field_mem_for_reg): Add handling of volatile
> bitfields.
>
> Index: gcc/expmed.c
> ===================================================================
> --- gcc/expmed.c 2012-11-27 19:09:18.000000000 +0000
> +++ gcc/expmed.c 2012-11-27 19:09:33.314634741 +0000
> @@ -372,6 +372,15 @@ adjust_bit_field_mem_for_reg (enum extra
> bitregion_end, MEM_ALIGN (op0),
> MEM_VOLATILE_P (op0));
> enum machine_mode best_mode;
> + if (MEM_VOLATILE_P (op0) && flag_strict_volatile_bitfields > 0)
> + {
> + while (iter.next_mode (&best_mode))
> + if (GET_MODE_SIZE (best_mode) == MEM_SIZE (op0))
> + return narrow_bit_field_mem (op0, best_mode, bitsize, bitnum,
> + new_bitnum);
> + return NULL_RTX;
> + }
> +
> if (iter.next_mode (&best_mode))
> {
> /* We can use a memory in BEST_MODE. See whether this is true for
next prev parent reply other threads:[~2012-11-27 22:45 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-03 11:10 Richard Sandiford
2012-11-03 11:13 ` [1/8] Handle TRUNCATE in make_extraction Richard Sandiford
2012-11-10 15:52 ` Eric Botcazou
2012-11-03 11:14 ` [2/8] Add adjust_bitfield_address_size Richard Sandiford
2012-11-10 15:53 ` Eric Botcazou
2012-11-03 11:16 ` [3/8] Add narrow_bit_field_mem Richard Sandiford
2012-11-10 16:02 ` Eric Botcazou
2012-11-03 11:21 ` [4/8] Add bit_field_mode_iterator Richard Sandiford
2012-11-13 12:44 ` Eric Botcazou
2012-11-13 21:46 ` Richard Henderson
2012-11-13 22:05 ` Eric Botcazou
2012-11-15 12:11 ` Richard Sandiford
2012-11-15 20:39 ` Richard Henderson
2012-11-18 17:34 ` Richard Sandiford
2012-11-18 17:36 ` Richard Sandiford
2012-11-03 11:27 ` [5/8] Tweak bitfield alignment handling Richard Sandiford
2012-11-13 13:52 ` Eric Botcazou
2012-11-18 17:36 ` Richard Sandiford
2012-11-20 2:57 ` John David Anglin
2012-11-20 8:21 ` Mikael Pettersson
2012-11-20 10:32 ` Richard Sandiford
2012-11-20 19:56 ` Richard Sandiford
2012-11-20 22:11 ` Eric Botcazou
2012-11-03 11:28 ` [6/8] Add strict volatile handling to bit_field_mode_iterator Richard Sandiford
2012-11-13 13:57 ` Eric Botcazou
2012-11-15 12:25 ` Richard Sandiford
2012-11-15 17:10 ` Eric Botcazou
2012-11-15 17:47 ` Richard Sandiford
2012-11-15 19:32 ` Eric Botcazou
2012-11-18 17:36 ` Richard Sandiford
2012-11-03 11:39 ` [7/8] Replace mode_for_extraction with new interface Richard Sandiford
2012-11-03 11:41 ` [8/8] Add new optabs and use them for MIPS Richard Sandiford
2012-11-27 17:11 ` [0/8] Add optabs alternatives for insv, extv and extzv Ramana Radhakrishnan
2012-11-27 20:22 ` Richard Sandiford
2012-11-27 22:45 ` Ramana Radhakrishnan [this message]
2012-11-28 10:25 ` Richard Biener
2012-11-28 12:06 ` Ramana Radhakrishnan
2012-11-28 12:51 ` Richard Biener
2012-11-28 13:58 ` Richard Sandiford
2012-11-28 23:19 ` Eric Botcazou
2012-11-29 10:31 ` Richard Sandiford
2012-11-29 15:31 ` Eric Botcazou
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=CAJA7tRYbJROUR5HAHhoLRu73+8Jr5ocj3mR3CLxiTZRJLuzNBg@mail.gmail.com \
--to=ramana.gcc@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ramrad01@arm.com \
--cc=rdsandiford@googlemail.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).