Recent searches

No recent searches

Search options

Only available when logged in.
shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

268
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.0

#sparc

1 post1 participant0 posts today
Continued thread
petersuber

#SPARC has released its own new info on the new #NIH #OpenAccess policy.
sparcopen.org/wp-content/uploa

Excerpt:

<blockquote>
● The Policy requires immediate public access to articles -- #embargoes are no longer allowed.
● NIH reiterates authors do not have to pay a fee to comply with the Policy.
● The Policy applies to manuscripts accepted for publication on or after July 1, 2025. This means the Policy will apply to existing grants if an article is accepted on or after that date.
● The Policy requires that final peer-reviewed manuscripts be submitted to #PubMedCentral (#PMC) upon acceptance to be made publicly available immediately upon publication.
● The Policy requires that grantees explicitly grant the NIH the right to make the manuscript available in PMC without an embargo.
● The Policy does not explicitly grant full reuse rights of the manuscript to the public.
</blockquote>

#Copyright#GreenOA#Medicine
Freya (it/its)𒀭𒈹𒍠𒊩

Is there anyone in #Australia or #NZ, or who would be willing to ship to NZ, who could donate a #SPARC #Solaris (sun4u/sun4v) machine to the building effort for FractalKit? We're running up against some limits and some really bad time sinks, doing all of this on a 650MHz #UltraSPARC IIe is.... really really painful. We know this is a long shot, but if anyone out there has a machine they could donate to this we would be immensely thankful. This porting effort is really important to us but it's not going to be actually useful if a single library takes a day to compile. If you can't help, then please boost? @SolarisDiaspora

Freya (it/its)𒀭𒈹𒍠𒊩

Is there anyone in #Australia or #NZ, or who would be willing to ship to NZ, who could donate a #SPARC #Solaris (sun4u/sun4v) machine to the building effort for FractalKit? We're running up against some limits and some really bad time sinks, doing all of this on a 650MHz #UltraSPARC IIe is.... really really painful. We know this is a long shot, but if anyone out there has a machine they could donate to this we would be immensely thankful. This porting effort is really important to us but it's not going to be actually useful if a single library takes a day to compile.

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

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?

#AskFedi#Binutils#GCC
Replied to Sun Microdevil Pte Ltd
Kevin Karhan :verified:

@koakuma @techokami also #UltraSparcT2 as cool as it was at release (including dual 10Gbit-NICs and hardware RNG on die) has a lot of things noone would want to deal with in 2024 (i.e. DDR2-FBDIMMs).

  • Plus #RISCv unlike #SPARCv9 amd #OpenPOWER was designed on a clean slate in academia by people who had dealt with #RISC & #CISC architectures and needed something #OpenSource as they can't just violate NDAs nilly-willy for teaching.

Pretty shure @stman could write an entire curriculum on why #SPARC, #PowerPC, #s390x and even #ARM / #ARM64 should not be pursued and why #mc68k died alongside the unfixable-by-design mess that is #ix86 & #amd64.

  • Plus RISCv's ISA has been an #OpenStandard from the get go, whereas the efforts by #Oracle nee #Sun and #IBM were mostly done in reaction to it and to keep the few invested licensees and co-designers onboard and not drop the platform entirely...

Look, I'd love to get my hands on some Sun SPARC Hardware but aside from making my room hot and noisy there isn't much to justify blowing likely over half a Euro per hour (electricity price: € 0,40/kWh) just to have it up and running, as compared to a #PiCluster like those @geerlingguy had built multiple times are more practical.

  • For comparison: It's like driving a 2011 Ford CVPI-71 with a 11,9l SONNY'S SAR-729 engine for commuting from Leverkusen to Köln when there's ample of affordable, reliable and fast public transport that gets me faster from Opladen to Deutz than it takes to drive up the 15th deck of a parking garage just to find a spot to park that 5,7m long street yacht where one can climb out of it from the doors and not the trunk!

And that's just bottom-billing, low-cost ARM SoC tech designed for a price tag (to the point that until the #Pi5 they neither included a power button nor #RTC onboard!

  • OFC RISC-V is still 5-25+ years behind #ARMv9 solely based off #patents, #budget and #PersonnelHours invested in it, so it's barely getting on-par with 10-20yr old ARM devices in terms.of power and support.
#armv9#patents#budget
TrendingLive feeds
About