From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Ian Lance Taylor <iant@google.com>,
Uros Bizjak <ubizjak@gmail.com>,
Igor Zamyatin <izamyatin@gmail.com>,
gcc@gcc.gnu.org
Subject: Re: RFC: PATCH: Require and use int64 for x86 options
Date: Thu, 28 Jul 2011 14:34:00 -0000 [thread overview]
Message-ID: <CAMe9rOp6L9M7PQ0Pyh2V90_OvN29Ja_DcVd6KpnXHehNFksr_g@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOrx_WEqTCNV7inJ3ZFsF5KckVLxqn-DtuYsXUM+SdFwuA@mail.gmail.com>
On Wed, Jul 27, 2011 at 2:37 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Wed, Jul 27, 2011 at 2:23 PM, Joseph S. Myers
> <joseph@codesourcery.com> wrote:
>> On Wed, 27 Jul 2011, H.J. Lu wrote:
>>
>>> ; Maximum number of mask bits in a variable.
>>> MaxMaskBits
>>> ix86_isa_flags = 64
>>>
>>> It mark ix86_isa_flags as 64bit. Any comments?
>>
>> The patch won't work as is. set_option, for example, casts a pointer to
>> (int *), and stores a mask that came from option->var_value, which is an
>> int, so this won't work with option fields not of type int or values that
>> don't fit in int; you'd need to check all uses of CLVC_BIT_CLEAR and
>> CLVC_BIT_SET in the source tree to adapt things for the possibility of
>> wider mask fields, and track the type of each such field.
>
> We will prepare a separate patch.
>
>> Independently, I approve of setting need_64bit_hwint for all x86 targets,
>> but your patch doesn't achieve the expected simplification. In
>> config.gcc, there are settings for various individual targets that should
>> be removed once it's set in one place for all x86 targets. In
>> libcpp/configure.ac, similarly the cases for i[34567]86-*-darwin*
>> i[34567]86-*-solaris2.1[0-9]* x86_64-*-solaris2.1[0-9]*
>> i[34567]86-w64-mingw* i[34567]86-*-linux* (the last only if
>> --enable-targets=all) should all be removed as obsolete once
>> i[34567]86-*-* is there along with x86_64-*-*.
>>
>
> Is this patch OK for trunk?
>
> Thanks.
>
> H.J.
> ----
> gcc/
>
> 2011-07-27 H.J. Lu <hongjiu.lu@intel.com>
>
> * config.gcc: Set need_64bit_hwint to yes for x86 targets.
>
> libcpp/
>
> 2011-07-27 H.J. Lu <hongjiu.lu@intel.com>
>
> * configure.ac: Set need_64bit_hwint to yes for x86 targets.
> * configure: Regenerated.
>
Bootstrapped on Linux/ia32. I am checking it in.
Thanks.
--
H.J.
next prev parent reply other threads:[~2011-07-28 14:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 17:00 H.J. Lu
2011-07-27 17:40 ` Uros Bizjak
2011-07-27 18:05 ` H.J. Lu
2011-07-27 21:37 ` Joseph S. Myers
2011-07-27 22:00 ` H.J. Lu
2011-07-28 14:34 ` H.J. Lu [this message]
2011-08-04 18:08 ` H.J. Lu
2011-08-04 22:09 ` H.J. Lu
2011-08-04 22:46 ` Joseph S. Myers
2011-08-04 23:44 ` H.J. Lu
2011-08-05 0:50 ` H.J. Lu
2011-07-29 9:53 ` Paolo Bonzini
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=CAMe9rOp6L9M7PQ0Pyh2V90_OvN29Ja_DcVd6KpnXHehNFksr_g@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=izamyatin@gmail.com \
--cc=joseph@codesourcery.com \
--cc=ubizjak@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).