Re: [oi-dev] Build of gcc-7.3.0 stops with linker errors

[Richard Lowe]

On Sat, May 26, 2018 at 12:26 PM Gary Mills  wrote:

> On Sat, May 26, 2018 at 03:32:55PM +0300, Igor Kozhukhov wrote:
> >
> > we have tried to do some research for GNU AS replacement with
> > illumos build on SPARC - but GNU binutils (GAS) should be updated a
> little.
> > i have filed som bugs and they was resolved, but not at all.
>
> Are you saying that gas for SPARC is not a general-purpose assembler,
> that it's only designed to handle the output from the compiler?
>

That's not the case.

Though, for what it's worth, using the assembler through the compiler
front-end would simplify things a lot (though you'd have to rename any
files that needed the preprocessor .S rather than .s).

-- Rich
-- 

-- Rich
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Build of gcc-7.3.0 stops with linker errors

[Gary Mills]

On Sat, May 26, 2018 at 03:32:55PM +0300, Igor Kozhukhov wrote:
> 
> we have tried to do some research for GNU AS replacement with
> illumos build on SPARC - but GNU binutils (GAS) should be updated a little.
> i have filed som bugs and they was resolved, but not at all.

Are you saying that gas for SPARC is not a general-purpose assembler,
that it's only designed to handle the output from the compiler?

Files written in assembler would be a problem then.

> we have used very old SUN AS doc - found by google.

Yes, I've found that.  It should be adequate.

> GNU AS for sparc documented in sources.

In the gas source, do you mean?

> but - not finished updates - still need additional work.
> i can try to found a branch on dilos-illumos with updates,
> but it is outdated and should be rebased to latest.
> I have no time right now for this work.

Even knowing the remaining bugs in gas would be useful


-- 
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Build of gcc-7.3.0 stops with linker errors

[Alan Coopersmith]

On 05/26/18 05:26 AM, Gary Mills wrote:
> On Thu, May 24, 2018 at 11:17:35AM -0400, Richard Lowe wrote:
>>They're not different enough to be more than theoretically mechanical
>>changes, but are (just) different enough you may not be able to
>>_actually_ do it all mechanically.
>>Assembler being much more rigid, you'll have an easier time comparing
>>the outputs to make sure you're doing the same things -- and of course,
>>you having a SPARC to test really helps.
> 
> Are there reference documents that describe the Sun and GNU formats
> for SPARC assembly language?  That would make it easier to translate
> correctly from one to the other.

For the Sun format, see:

https://docs.oracle.com/cd/E37838_01/html/E61063/index.html

-alan-

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] GCC 8 build status

[Aurélien Larcher]

Aside from:

developer/clang-40
developer/gcc-5
developer/gcc-6
developer/gcc-7
runtime/sbcl

All the packages have been recompiled with gcc-8 and published to the
http://pkg.openindiana.org/gcc-6 repository.

I updated two machines for testing and two issues are present:
1) For some reason Firefox has a default User-Agent containing non-ASCII
characters that upset webservers. Overriding it with another string is
enough to work around the problem.
2) Similarly to tmux when linked to values-xpg(4|6).o, mate-terminal is
killed with CTRL^C instead of sending the signal.

I initially encountered some terminal resizing issue through ssh but cannot
reproduce them now after rebuilding and republishing another batch of
components.








On Fri, May 25, 2018 at 10:29 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

> Updated list:
>
> developer/clang-40
> developer/gcc-5
> developer/gcc-6
> developer/gcc-7
> developer/golang-18
> library/webkitgtk
> runtime/sbcl [coredump, sorry Alexander :( ]
>
> I have tested the resulting packages on my workstation and laptop
> (currently typing on the X230).
>
>>
>
> --
> ---
> Praise the Caffeine embeddings
>



-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Build of gcc-7.3.0 stops with linker errors

[Igor Kozhukhov]

On May 26, 2018, at 3:26 PM, Gary Mills  wrote:
> 
> On Thu, May 24, 2018 at 11:17:35AM -0400, Richard Lowe wrote:
>>   They're not different enough to be more than theoretically mechanical
>>   changes, but are (just) different enough you may not be able to
>>   _actually_ do it all mechanically.
>>   Assembler being much more rigid, you'll have an easier time comparing
>>   the outputs to make sure you're doing the same things -- and of course,
>>   you having a SPARC to test really helps.
> 
> Are there reference documents that describe the Sun and GNU formats
> for SPARC assembly language?  That would make it easier to translate
> correctly from one to the other.

Hi Garry,
we have tried to do some research for GNU AS replacement with illumos build on 
SPARC - but GNU binutils (GAS) should be updated a little.
i have filed som bugs and they was resolved, but not at all.
we have used very old SUN AS doc - found by google.
GNU AS for sparc documented in sources.
but - not finished updates - still need additional work.
i can try to found a branch on dilos-illumos with updates, but it is outdated 
and should be rebased to latest.
I have no time right now for this work.

for your gcc7 bootstrap issue.
as i remember - it was gcc5 last with gcc5+SUN AS possibe bootstrap.
from gcc6 on SPARC - we are using gcc6 + GNU AS (GAS) bootstrap.
also, we are using 64bit as default.

-Igor

> -- 
> -Gary Mills-  -refurb--Winnipeg, Manitoba, Canada-
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Build of gcc-7.3.0 stops with linker errors

[Gary Mills]

On Thu, May 24, 2018 at 11:17:35AM -0400, Richard Lowe wrote:
>They're not different enough to be more than theoretically mechanical
>changes, but are (just) different enough you may not be able to
>_actually_ do it all mechanically.
>Assembler being much more rigid, you'll have an easier time comparing
>the outputs to make sure you're doing the same things -- and of course,
>you having a SPARC to test really helps.

Are there reference documents that describe the Sun and GNU formats
for SPARC assembly language?  That would make it easier to translate
correctly from one to the other.


-- 
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev