[fpc-devel] -i and -Cp

Mark Morgan Lloyd markMLl.fpc-devel at telemetry.co.uk
Wed Oct 17 20:36:02 CEST 2012


Tomas Hajny wrote:
> On Wed, October 17, 2012 16:25, Pierre Free Pascal wrote:
>> You are right:
>> muller at deluxe:~/pas/test$ ppcsparc hello
>> muller at deluxe:~/pas/test$ ppcsparc hello -CpXX
>> Error: Illegal parameter: -CpXX
>> muller at deluxe:~/pas/test$ ppcsparc hello -Cp"sparc v7"
>> muller at deluxe:~/pas/test$ ppcsparc hello -Cp"sparc v8"
>> muller at deluxe:~/pas/test$ ppcsparc hello -Cp"sparc v9"
>> muller at deluxe:~/pas/test$ ppcsparc hello -Cp"sparc v19"
>> Error: Illegal parameter: -Cpsparc v19
>>
>> But I didn't find any use of cputype current_settings field
>> in compiler/sparc directory sources,
>> so the generated result should not change...
> 
> If the field/value isn't used yet, wouldn't it make sense to change the
> texts so that they use an underscore instead of space? I believe that it
> makes life easier for everyone and helps to avoid similar questions in the
> future. It seems that GCC uses just v7/v8/v9 (without "SPARC") so that the
> space doesn't seem to come from an attempt for alignment with GCC or
> something like that.

Or at least accepting just v8/v9 where there is no ambiguity. I note 
that some FPU designations already have underscores.

> Regarding Marks attempt - if I understand it correctly (based on
> information in Wikipedia ;-) ), Sparc v7 supports no HW multiplication /
> division. So a simple check may be to write a one liner containing
> multiplication, compiling it with any ppcsparc (or ppccrosssparc) while
> using the -s parameter and then checking the generated assembly for use of
> the mul/div asm instructions...

I'll take a look. However I stress that I've got absolutely nothing 
invested in SPARC v7 (AKA sun4c) and only marginal interest in Solaris 
7, so allowing that even the LEON processor supports v8 (as do sun4m and 
sun4d) I think v7 could be quietly dropped.

-- 
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]



More information about the fpc-devel mailing list