From: Uros Bizjak <ubizjak@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Yulia Koval <vaalfreja@gmail.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix pr67963
Date: Thu, 15 Oct 2015 07:53:00 -0000 [thread overview]
Message-ID: <CAFULd4Y4UiUaaNe0gJ7vGoDsVz8=3EHs0X1YXRydAmnGHCB-XQ@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOpC8-Jo_muo9_ogmck_wyM2FfxCpgeJts2ndA5m+GOdOg@mail.gmail.com>
On Wed, Oct 14, 2015 at 5:17 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Wed, Oct 14, 2015 at 8:15 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
>> On Wed, Oct 14, 2015 at 8:08 AM, Yulia Koval <vaalfreja@gmail.com> wrote:
>>> Hi,
>>>
>>> This patch fixes the issue:
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67963
>>>
>>> gcc/config/i386/i386.c (ix86_option_override_internal) Disable
>>> 80387 mask if lakemont target is set.
>>>
>>> diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c
>>> index 4c25c9e..db722aa 100644
>>> --- a/gcc/config/i386/i386.c
>>> +++ b/gcc/config/i386/i386.c
>>> @@ -4943,6 +4943,12 @@ ix86_option_override_internal (bool main_args_p,
>>> break;
>>> }
>>>
>>> + if (!strcmp (opts->x_ix86_arch_string, "lakemont"))
>>> + {
>>> + opts->x_target_flags &= ~MASK_80387;
>>> + opts_set->x_target_flags |= MASK_80387;
>>> + }
>>> +
>>> if (TARGET_X32 && (opts->x_ix86_isa_flags & OPTION_MASK_ISA_MPX))
>>> error ("Intel MPX does not support x32");
>>>
>>> Ok for trunk?
>>
>> We should add a bit to "struct pta" to indicate availability of
>> 80387 ISA and turn it off for lakemount if 90387 ISA hasn't be
>> turned on explicitly.
>
> Something like
Hm, I don't think introducing another flag is a good idea.
Better move -m80387 (together with -msof-float and -mhard-float) to
ISA flags and add corresponding PTA_80387 define.
Uros.
next prev parent reply other threads:[~2015-10-15 7:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 15:08 Yulia Koval
2015-10-14 15:15 ` H.J. Lu
2015-10-14 15:17 ` H.J. Lu
2015-10-15 7:53 ` Uros Bizjak [this message]
2015-10-15 11:45 ` Uros Bizjak
2015-10-15 16:57 ` Uros Bizjak
2015-10-15 16:59 ` H.J. Lu
2015-10-15 19:16 ` Uros Bizjak
2015-10-15 19:21 ` H.J. Lu
2015-10-15 19:31 ` Uros Bizjak
2015-10-16 6:45 ` Uros Bizjak
2015-10-16 9:37 ` Uros Bizjak
2015-10-16 10:33 ` H.J. Lu
2015-10-16 10:45 ` 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='CAFULd4Y4UiUaaNe0gJ7vGoDsVz8=3EHs0X1YXRydAmnGHCB-XQ@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=vaalfreja@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).