Am 06.07.2017 um 20:53 schrieb Jeff Law:
> Hmm, unfortunately I consistently get a call to into libgcc for the
> __builtin_ffs code rather than an ffs instruction. That's with a
> gcc-4.8.3 as well as with trunk compiler.
>
> Can you include "-v" output from compiling scsipi_base?
Hope this is r
On 07/06/2017 10:59 AM, Felix Deichmann wrote:
> Jeff,
>
> Am 29.06.2017 schrieb Jeff Law :
>> Ideally we'd like to have a testcase for this in the regression suite.
>>
>> If you could provide the .i file and options used which generated the
>> incorrect ffs instruction I can use the reduction too
Jeff,
Am 29.06.2017 schrieb Jeff Law :
> Ideally we'd like to have a testcase for this in the regression suite.
>
> If you could provide the .i file and options used which generated the
> incorrect ffs instruction I can use the reduction tools with a cross
> compiler to produce a nice simple test
On 06/29/2017 09:47 AM, co...@sdf.org wrote:
> Ping.
>
> On Tue, Jun 20, 2017 at 08:05:42PM +, co...@sdf.org wrote:
>> VAX' FFS as variable-length bit field instruction uses a "base"
>> operand of type "vb" meaning "byte address".
>> "base" can be 32 bits (SI) and due to the definition of
>> f
Ping.
On Tue, Jun 20, 2017 at 08:05:42PM +, co...@sdf.org wrote:
> VAX' FFS as variable-length bit field instruction uses a "base"
> operand of type "vb" meaning "byte address".
> "base" can be 32 bits (SI) and due to the definition of
> ffssi2/__builtin_ffs() with the operand constraint "m",
VAX' FFS as variable-length bit field instruction uses a "base"
operand of type "vb" meaning "byte address".
"base" can be 32 bits (SI) and due to the definition of
ffssi2/__builtin_ffs() with the operand constraint "m", code can be
emitted which incorrectly implies a mode-dependent (= longword, fo
