On Fri, 17 Apr 2015 17:22:13 +0200, Jan Kratochvil wrote:
> How to get 'volatile struct sv' GCC 'tree' type for:
> volatile struct sv { volatile struct sv *p; };
I have found out how it can work, even with no change on the GCC side:
Instead of current:
plugin_build_record_type:
The second release candidate for GCC 5.1 is available from
ftp://gcc.gnu.org/pub/gcc/snapshots/5.0.1-RC-20150418
and shortly its mirrors. It has been generated from SVN revision 11.
Because the release candidate uses 5.0.1 as its version (5.1.0 is
reserved for the GA 5.1 release only, see
On a x86_64 linux box I successfully built a gcc RC-20150418 toolchain
including binutils-2.25 and avr-libc r2473(svn).
I noticed some warnings in the logs:
../../../source/gcc-5.0.1-RC-20150418/gcc/vec.h:1048: warning: invalid
access to non-static data member âvec::m_vecdataâ of NULL object
Started with the latter. By the way, what is the policy concerning
getting write access to the wiki?
You are expected to ask one of the existing editors who's
willing to vouch for you to add you to the EditorGroup:
http://gcc.gnu.org/wiki/EditorGroup
Martin
Hi
with nios2-rtems on gcc 4.9.2, we are getting undefineds
for some atomic primitives. Are these implemented or is
some magic bit of configurery missing for nios-rtems?
__sync_fetch_and_add_4 is missing on a simple C++ IO streams
sanity test.
Thanks
-- Joel Sherrill
Ask me about RTEMS: a free
On 04/18/2015 07:35 PM, Joel Sherrill wrote:
Hi
with nios2-rtems on gcc 4.9.2, we are getting undefineds
for some atomic primitives. Are these implemented or is
some magic bit of configurery missing for nios-rtems?
__sync_fetch_and_add_4 is missing on a simple C++ IO streams
sanity test.
libg