Skip to content

Issues: volumit/tricore_gcc940_linux_bins

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

9 Open 1 Closed
9 Open 1 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Feature enhancement requested for parameter passing
#10 opened Jun 28, 2022 by volumit
recheck of gcc/g++/stdc++/gdb testuites for semihosting tests
#9 opened Jun 26, 2022 by volumit
enhance testsuite for tc161,tc162,tc16,tc18 compatibility
#8 opened Jun 26, 2022 by volumit
if tricore-gcc used without -mcpu wrong startup and libaries are taken
#6 opened Jun 26, 2022 by volumit
Consistency issues in gdb for target xml
#5 opened Jun 26, 2022 by volumit
Qemu does not continue after debug in semihosting with trace files and single stepping
#4 opened Jun 26, 2022 by volumit
ftell/fseek inconsistent behavior - see issue
#3 opened Jun 26, 2022 by volumit
C99 API related macros, such as _GLIBCXX_USE_C99_STDLIB and _GLIBCXX_USE_C99_STDIO are not defined by default. It lead to some C99 carry over API or some related C++ API can't work
#2 opened Jun 26, 2022 by volumit
tricore gdb crash when fopen is used in source
#1 opened Jun 14, 2022 by Changqing-JING
11
ProTip! Updated in the last three days: updated:>2024-12-17.