Hi Richard,
that's an excellent idea, I'll try to figure out to do that.
Thanks for the advice!
Nicolas
On 23/10/2020 19:29, Richard Biener wrote:
On October 23, 2020 7:49:04 PM GMT+02:00, "Nicolas König"
wrote:
Hello everyone,
I'm hoping to get shared coarrays for fortran (the devel/
Hi
Given that GNU attributes are not part of the standard..
I wonder if the following is expected to work?
__attribute__((__deprecated__))
extern "C" __attribute__((__visibility__("default")))
void foo ()
{
}
t.C:3:8: error: expected unqualified-id before string constant
3 | extern "C" __
Hi,
for the AMD64 alias x86_64 platform and the __int128_t [DW]type,
the first few lines of the __mulvDI3() function from libgcc2.c
| DWtype
| __mulvDI3 (DWtype u, DWtype v)
| {
| /* The unchecked multiplication needs 3 Wtype x Wtype multiplications,
| but the checked multiplication needs
Snapshot gcc-11-20201025 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20201025/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
I know compiling is exponenental when considering it compiles operating
systems, but can someone either implement or help me implement some kind of
singular security feature for the stack so hacks dont access the heap? Im
thinking the first few bytes would be some security software or feature (w
