[wwwdocs] PATCH Re: DWARF Version 5 Standard Released
On Wed, 15 Feb 2017, Michael Eager wrote: > The DWARF Debugging Information Format Standards Committee is pleased > to announce the availability of Version 5 of the DWARF Debugging Format > Standard. This patch, which I just applied, updates the GCC 7 release notes accordingly. (Now it's only GCC 7 that is upcoming, not DWARF 5 as well. ;-) Gerald Index: changes.html === RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-7/changes.html,v retrieving revision 1.64 diff -u -r1.64 changes.html --- changes.html16 Feb 2017 17:46:55 - 1.64 +++ changes.html19 Feb 2017 21:54:05 - @@ -141,7 +141,7 @@ UndefinedBehavior Sanitizer now diagnose arithmetic overflows even on arithmetic operations with generic vectors. - The upcoming version 5 of the Version 5 of the http://www.dwarfstd.org/Download.php";>DWARF debugging information standard is supported through the -gdwarf-5 option. The DWARF version 4 debugging information remains the
gcc-7-20170219 is now available
Snapshot gcc-7-20170219 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/7-20170219/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 7 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision 245582 You'll find: gcc-7-20170219.tar.bz2 Complete GCC MD5=55bf7d14a2cf9179b72d2e1776f2c8ed SHA1=13d86c439396a53690e2772e3d58c9422558e03d Diffs from 7-20170212 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-7 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
[contribution] C11 threads implementation for Unix and Windows environments
Hi, I am actually working on C11 threads implementation for Unix and Windows environments, and I would like to know if the GCC community could be interested. This is the github repository for my implementation : https://github.com/eau-de-la-seine/c-standard-threads I have implemented almost all the thrd_ and mtx_ functions (I need to do more tests), only those two following functions are not implemented yet : thrd_sleep and mtx_timed_lock (they are time related). I would be glad to contribute. Best regards,
Re: [contribution] C11 threads implementation for Unix and Windows environments
On 2017/2/20 6:59, Gkn Knc wrote: > I am actually working on C11 threads implementation for Unix and > Windows environments, and I would like to know if the GCC community > could be interested. The C library isn't part of gcc, so I am afraid this isn't the right place for implementation of it. libc or mingw-w64 whatsoever seems more appropriate. GCC's threading support is based on another abstraction layer. See comments in `gthr.h`. > This is the github repository for my implementation : > https://github.com/eau-de-la-seine/c-standard-threads A quick view of the source code discovers a few problems: 1. Please use reserved identifiers for implementation-specific macros or entities, so you don't get compiler errors due to name conflict with user-defined macros. 2. #include'ing windows.h in a header is almost always a bad idea. If you want `HANDLE`, for example, use `void *`. 3. CC-BY-NC-ND is overstrict. Consider removing NC. 4. The prototype of C11 thread procedure [`int (void *)`] is incompatible with that of pthread [`void *(void *)`] and WinAPI [`unsigned long __stdcall (void *)`]. Casting a C11 one then passing the result to `pthread_create()` or `CreateThread()` is certainly undefined behavior. 5. On x86 Windows, the stack pointer of a thread created by `CreateThread()` isn't aligned to a 16-byte boundary, but today GCC assumes it is. This could result in segment faults once SSE is enabled on x86. Please use `_beginthreadex()` instead. 6. The Windows mutex objects are quite heavyweight for in-process synchronization. You probably need to write a user-space one yourself or use the native CRITICAL_SECTION. 7. Condition variables are left unimplemented. > I have implemented almost all the thrd_ and mtx_ functions (I need to > do more tests), only those two following functions are not implemented > yet : thrd_sleep and mtx_timed_lock (they are time related). You haven't implemented condition variables and once initialization either, which makes a thread library almost unusable. > I would be glad to contribute. Best regards, Good luck. -- Best regards, ltpmouse
Re: [contribution] C11 threads implementation for Unix and Windows environments
Hello Gokan, you may have a look at: https://svnweb.freebsd.org/base/head/lib/libstdthreads/ -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
