Query
Wednesday 06 February 2019
2019-02-06 23:24:08 (3 years ago) by Henrik Grubbström (Grubba) <grubba@grubba.org>
- pike/src/code/sparc.c (+2/-1)(3 lines)
branch: bill/debugger-concept
Compiler [Sparc]: Fixed typo in previous commit.
- pike/src/code/sparc.c (+46/-9)(55 lines)
branch: bill/debugger-concept
Compiler [Sparc]: Improved support for large addresses.
It seems gcc on Linux/sparc64 places code at 0x10000000000
(out of reach for the generated code, which only supported
addresses up to and including 0x3ffffffff).
The maximum supported address is now 0xfffffffffff.
Monday 07 January 2019
2019-01-07 17:06:39 (3 years ago) by Henrik Grubbström (Grubba) <grubba@grubba.org>
- pike/src/code/sparc.c (+2/-1)(3 lines)
branch: master
Compiler [Sparc]: Fixed typo in previous commit.
2019-01-07 15:35:11 (3 years ago) by Henrik Grubbström (Grubba) <grubba@grubba.org>
- pike/src/code/sparc.c (+46/-9)(55 lines)
branch: master
Compiler [Sparc]: Improved support for large addresses.
It seems gcc on Linux/sparc64 places code at 0x10000000000
(out of reach for the generated code, which only supported
addresses up to and including 0x3ffffffff).
The maximum supported address is now 0xfffffffffff.
Thursday 05 July 2018
2018-07-05 13:24:29 (4 years ago) by Henrik Grubbström (Grubba) <grubba@grubba.org>
- pike/src/sscanf.c (+21/-7)(28 lines)
branch: master
Build [sparc]: Workaround for compiler bug in ~ gcc 4.7.4.
Gcc 4.7.4 and others "optimize" away calls to memcpy(), and replace
them with direct (unaligned) memory accesses. This generated broken
code for eg %F on sparc and other architectures that don't allow
unaligned memory accesses.
cf https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50569
Note that the patch mentioned in the above bug report is in gcc 4.7.4,
but isn't sufficient.
We work around the issue by forcing the float extractor functions
to not be inlined on such architectures.
Friday 27 January 2017
2017-01-27 15:03:29 (5 years ago) by Henrik Grubbström (Grubba) <grubba@grubba.org>
- pike/src/code/sparc.c (+83/-56)(139 lines)
branch: 8.1
Compiler [sparc]: Use string_builder_append_disassembly().
Also some minor formatting changes for the ld* and st* opcodes.
Saturday 23 May 2015
2015-05-23 23:38:50 (7 years ago) by Henrik Grubbström (Grubba) <grubba@grubba.org>
- pike/src/code/README.txt (+6/-0)(6 lines)
- pike/src/code/sparc.c (+6/-0)(6 lines)
- pike/src/code/sparc.h (+4/-0)(4 lines)
- pike/src/interpret_functions.h (+7/-0)(7 lines)
branch: 8.1
Total 23
Compiler [sparc]: Added kludge to fix the code-generator for sparc.
Some of the branch opcodes were broken on sparc when PIKE_DEBUG
wasn't active. This is a temporary workaround.
Thursday 04 December 2014
2014-12-04 20:25:04 (7 years ago) by Henrik Grubbström (Grubba) <grubba@grubba.org>
- pike/src/code/sparc.c (+7/-4)(11 lines)
branch: bill/master_archive_support
[sparc] Fixed bug introduced by the svalue renumbering.
The svalue type fields were set from a dirty register when pushing
the zero integer.
Fixes the fatal "Invalid type 120 in svalue at xxxxxxxx.", and similar.
Sunday 05 January 2014
2014-01-05 13:48:50 (8 years ago) by Henrik Grubbström (Grubba) <grubba@grubba.org>
- pike/src/code/sparc.c (+7/-4)(11 lines)
branch: 8.0
[sparc] Fixed bug introduced by the svalue renumbering.
The svalue type fields were set from a dirty register when pushing
the zero integer.
Fixes the fatal "Invalid type 120 in svalue at xxxxxxxx.", and similar.