This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Use flag_general_regs_only with -mgeneral-regs-only


On Tue, May 24, 2016 at 12:06 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Tue, May 24, 2016 at 11:44 AM, Uros Bizjak <ubizjak@gmail.com> wrote:
>> On Tue, May 24, 2016 at 8:15 PM, Uros Bizjak <ubizjak@gmail.com> wrote:
>>> On Tue, May 24, 2016 at 7:18 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
>>>
>>>>> Oh, target_flags is only a 32bit integer :(. Is there a reason it
>>>>> can't be extended to HOST_WIDE_INT, as is the case with
>>>>> ix86_isa_flags?
>>>>
>>>> target_flags is generic, not target specific.  I want to limit my
>>>> change to x86 backend and -mgeneral-regs-only doesn't need
>>>> to use target_flags .
>>>
>>> I have thrown together a quick patch that defines target_flags as HOST_WIDE_INT.
>>>
>>> (Patch still needs a small correction, so opth-gen.awk will emit
>>> HOST_WIDE_INT_1 for MASK_* defines, have to go now, but I was able to
>>> compile functional x86_64-apple-darwin15.5.0 crosscompiler.)
>>
>> And here is attached complete (but untested!!) patch that should "just
>> work"(TM).
>>
>
> -mgeneral-regs-only doesn't need to use target_flags and it shouldn't
> use target_flags.
>

Use target_flags won't hurt -mgeneral-regs-only.   I have no problem
with it.

-- 
H.J.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]