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: PING: PATCH: Use int64 for x86 options
Date: Tue, 09 Aug 2011 13:32:00 -0000 [thread overview]
Message-ID: <CAMe9rOp9rGjjTzP-Xi_q8+kfHLLQe8=z3_rW02CUSAvi=R=7wg@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOpKsuR81=VETqcu9qtVa8r44t3bRZRE10kn-JzhHzOi4A@mail.gmail.com>
Is this OK for trunk?
On Sun, Aug 7, 2011 at 7:18 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Sat, Aug 6, 2011 at 9:05 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
>> Ping. AVX2 support depends on this patch.
>>
>
>>> ---
>>> 2011-08-04 H.J. Lu <hongjiu.lu@intel.com>
>>> Igor Zamyatin <igor.zamyatin@intel.com>
>>>
>>> * hwint.h (HOST_WIDE_INT_1): New.
>>>
>>> * opt-functions.awk (switch_bit_fields): Initialize the
>>> host_wide_int field.
>>> (host_wide_int_var_name): New.
>>> (var_type_struct): Check and return HOST_WIDE_INT.
>>>
>>> * opt-read.awk: Handle HOST_WIDE_INT for "Variable".
>>>
>>> * optc-save-gen.awk: Support HOST_WIDE_INT on var_target_other.
>>>
>>> * opth-gen.awk: Use HOST_WIDE_INT_1 on HOST_WIDE_INT. Properly
>>> check masks for HOST_WIDE_INT.
>>>
>>> * opts-common.c (set_option): Support HOST_WIDE_INT Flag_var.
>>>
>>> * opts.h (cl_option): Add cl_host_wide_int. Change var_value
>>> to HOST_WIDE_INT.
>>>
>>> * config/i386/i386-c.c (ix86_target_macros_internal): Replace int
>>> with HOST_WIDE_INT for isa_flag.
>>> (ix86_pragma_target_parse): Replace int with HOST_WIDE_INT for
>>> isa variables.
>>>
>>> * config/i386/i386.c (ix86_target_string): Replace int with
>>> HOST_WIDE_INT for isa. Use HOST_WIDE_INT_PRINT to print isa.
>>> (ix86_target_opts): Replace int with HOST_WIDE_INT on mask.
>>> (pta_flags): Removed.
>>> (PTA_XXX): Redefined as (HOST_WIDE_INT_1 << X).
>>> (pta): Use HOST_WIDE_INT on flags.
>>> (builtin_isa): Use HOST_WIDE_INT on isa.
>>> (ix86_add_new_builtins): Likewise.
>>> (def_builtin): Use HOST_WIDE_INT on mask.
>>> (def_builtin_const): Likewise.
>>> (builtin_description): Likewise.
>>>
>>> * config/i386/i386.opt (ix86_isa_flags): Replace int with
>>> HOST_WIDE_INT.
>>> (ix86_isa_flags_explicit): Likewise.
>>> (x_ix86_isa_flags_explicit): Likewise.
>>>
>>
>>
>>
>> --
>> H.J.
>>
>
> HOST_BITS_PER_WIDE_INT isn't defined in target library.
> I need to check if HOST_BITS_PER_WIDE_INT is defined
> first. Here is the updated patch.
>
>
>
> --
> H.J.
>
--
H.J.
next prev parent reply other threads:[~2011-08-09 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 16:05 H.J. Lu
2011-08-08 2:18 ` H.J. Lu
2011-08-09 13:32 ` H.J. Lu [this message]
2011-08-09 14:07 ` Joseph S. Myers
2011-08-09 14:22 ` H.J. Lu
2011-08-16 13:09 ` H.J. Lu
2011-08-16 13:48 ` Joseph S. Myers
2011-08-17 19:28 ` Joseph S. Myers
2011-08-17 20:27 ` H.J. Lu
2011-08-17 20:35 ` Joseph S. Myers
2011-08-17 20:41 ` H.J. Lu
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='CAMe9rOp9rGjjTzP-Xi_q8+kfHLLQe8=z3_rW02CUSAvi=R=7wg@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).