Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
norden.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Moin! Dies ist die Mastodon-Instanz für Nordlichter, Schnacker und alles dazwischen. Folge dem Leuchtturm.

Administered by:

Server stats:

3.6K
active users

norden.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#sparc

0 posts0 participants0 posts today
Public
bg nerilex

Ich habe gerade ein paar #retro bzw. #vintage Computer abzugeben.

Folgenden Maschinen suchen ein neues Zuhause:

* #Sun #sparc station IPC
* Sun Ultra 5 (64 bit sparc)
* HP 712/60 (gecko #PARISC)
* #MicroVAX II (BA123)

Die Geräte müssten in Bochum abgeholt werden.

Von der #VAX habe ich gerade noch keine Bilder, da die noch im Keller sitzt.

Mir genügt es, wenn die Maschinen ein liebevolles Zuhause finden, und nicht dem Elektroschrott anheim fallen müssen.

🔄 Boosts welcome

Ein kleiner Turm aus eine Sun Ultra 5 Workstation (PizzaBox), einer HP 172/60 Gecko (PizzaBox) und einer Sun Spacrstation IPC (LunchBox). Darauf liegen noch eine Sun Tastatur und Maus.
Public *
Sun Microdevil Pte Ltd

Anyone here familiar with SPARC binutils internals? I'm having a rather odd case where the same instruction (and same binary sequence) gets interpreted differently depending on who compiles it :cirnothinking:

Say, I have this `decode.s` file containing the following line:
decode: addxccc %g0, %g0, %g0

One VIS3 instruction, very simple. Then assemble it with both gcc and clang:
gcc -mcpu=niagara4 -c decode.s -o decode-gcc.o
clang -mcpu=niagara4 -c decode.s -o decode-clang.o

And now, if I run objdump on the files, the results are different:
decode-clang.o: file format elf64-sparc

Disassembly of section .text:

0000000000000000 <decode>:
0: 81 b0 02 60 unknown

Compare with GCC's:
decode-gcc.o: file format elf64-sparc

Disassembly of section .text:

0000000000000000 <decode>:
0: 81 b0 02 60 addxccc %g0, %g0, %g0

In both cases the binary stream is the same, but why does objdump decodes it as "unknown" with the clang-built file?

Edit: found it, seems like GCC sets something in the attribute section:

Attribute Section: gnu
File Attributes
Tag_GNU_Sparc_HWCAPS: vis3

Though as far as I can tell other than odd objump output it doesn't seem to affect binary execution, etc.

#AskFedi#Binutils#GCC
Replied in thread
Public
George Macgregor

@gedankenstuecke

Excellent blog post, Bastian -- thank you very much for drawing it to my attention. "Vorauseilender Gehorsam" -- what a useful concept!

You used the words 'disheartening', 'bleak', 'infuriating' about @sparc. These chime with me too. 'Disappointing' would be another.

At least we have @SPARC_Europe which remains committed to DEI, as well as committed to defending openness in the "face of political and technological developments".

#SPARC#OpenScience#OpenResearch
ExploreLive feeds
About