volumit

See also: https://github.com/volumit/tricore_gcc940_linux_bins/issues/1#issuecomment-1167575076 ``#include int main(int argc, char *argv[]) { printf("tcargc %d\n",argc); for (int i=0; i

avoid issues of https://github.com/volumit/tricore_gcc940_linux_bins/issues/1

even if the difference between the tricore implemtations are mininmal, an additional robustness check is needed to ensure compatiblity and no pitfalls like in https://github.com/volumit/tricore_gcc940_linux_bins/issues/1 wil happen.

https://github.com/volumit/tricore_gcc940_linux_bins/issues/1 /home/dummy/tricore_940_linux/bin/tricore-elf-gcc -Xlinker -Map=output.map -o test_read_file.elf test_read_file.c see output.map In addition qemu needs an extension that it fails for illegal mem access and startup addr has to unified.

https://github.com/volumit/tricore_gcc940_linux_bins/issues/1 including wrong ioread (gdb) target remote:1234 Remote debugging using :1234 warning: while parsing target description (at line 1): Target description specified unknown architecture "TriCore:V1_6_2" warning: Could not load XML...

https://github.com/volumit/tricore_gcc940_linux_bins/issues/1#issuecomment-1160060786 /home/dummy/qemu_tricore_6250/bin/qemu-system-tricore -display none -M tricore_tsim162 -semihosting -s -d in_asm,nochain -D ./qemutrace.txt -kernel ./test_read_file.elf IN: _open_r 0x80001a32: 0f82 mov %d15,0 0x80001a34: 0820 sub.a %sp,8 0x80001a36: 4c40 mov.aa %a12,%a4 0x80001a38: fd000091...

https://github.com/volumit/tricore_gcc940_linux_bins/issues/1#issuecomment-1160060786 potential issue with ftell and fseek

https://github.com/volumit/tricore_gcc940_linux_bins/issues/1#issuecomment-1161284503 confirmed, but actually it is unclear if it is a gcc fork issue at all or a tricore specific. Was able to reproduce it with gcc tricore. echo |...