Steve Ellcey writes:
> On Sat, 2014-01-25 at 20:34 +, Richard Sandiford wrote:
>
>> Yeah, I've been trying to use separate variables for new flags.
>> That's why a lot of the MIPS options have discrete TARGET_… variables
>> (defined via Var(TARGET_…)). target_flags should only really be neede
On Sat, 2014-01-25 at 20:34 +, Richard Sandiford wrote:
> Yeah, I've been trying to use separate variables for new flags.
> That's why a lot of the MIPS options have discrete TARGET_… variables
> (defined via Var(TARGET_…)). target_flags should only really be needed
> for options whose defaul
"Steve Ellcey " writes:
> Richard,
>
> While experimenting with a local GCC change I added two new Masks to
> mips.opt and ran into a build failure about too many masks:
>
> ./options.h:4172:2: error: #error too many target masks
>
> It looks like we already have 31 Masks in the MIPS mips.opt file
On Fri, Jan 24, 2014 at 3:20 PM, Steve Ellcey wrote:
> Richard,
>
> While experimenting with a local GCC change I added two new Masks to
> mips.opt and ran into a build failure about too many masks:
>
> ./options.h:4172:2: error: #error too many target masks
>
> It looks like we already have 31 Ma
Richard,
While experimenting with a local GCC change I added two new Masks to
mips.opt and ran into a build failure about too many masks:
./options.h:4172:2: error: #error too many target masks
It looks like we already have 31 Masks in the MIPS mips.opt file and 32
is the limit. It looks like t
