aboutsummaryrefslogtreecommitdiff
path: root/newlib/libc/stdlib/wcstoll.c
diff options
context:
space:
mode:
authorStafford Horne <shorne@gmail.com>2025-03-28 10:09:27 +0000
committerCorinna Vinschen <corinna@vinschen.de>2025-03-31 10:59:53 +0200
commit3955b88056995bcaf9abe96eed6eaae12435c650 (patch)
tree278ac8c97d6b1ad04cbdc9240dadf31045d049f5 /newlib/libc/stdlib/wcstoll.c
parentac28fce85cc4d8f85c2cf10bb52d39f33ec38ed6 (diff)
downloadnewlib-3955b88056995bcaf9abe96eed6eaae12435c650.zip
newlib-3955b88056995bcaf9abe96eed6eaae12435c650.tar.gz
newlib-3955b88056995bcaf9abe96eed6eaae12435c650.tar.bz2
or1k: Fix compilation for __OR1K_MULTICORE__ builds
When building newlib for multicore environments we specify __OR1K_MULTICORE__ which switches the build to allocate one struct _or1k_reent per CPU dynamiocally. This was using a strange definition of (*_or1k_reent)[], and causing the following compiler error: ./gnu-toolchain/newlib/libgloss/or1k/impure.c: In function ‘_or1k_reent_init’: ./gnu-toolchain/newlib/libgloss/or1k/impure.c:121:21: error: assignment to ‘struct .. 121 | _or1k_reent = (struct _or1k_reent*) _sbrk_r(0, memsize); | Fix this compiler error by changing the or1k_reent definition to a pointer to structs. Signed-off-by: Stafford Horne <shorne@gmail.com>
Diffstat (limited to 'newlib/libc/stdlib/wcstoll.c')
0 files changed, 0 insertions, 0 deletions