public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
@ 2021-04-15 11:14 swilde@sha-bang.de
  2021-04-15 12:18 ` [Bug jit/100096] " jakub at gcc dot gnu.org
                   ` (30 more replies)
  0 siblings, 31 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2021-04-15 11:14 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

            Bug ID: 100096
           Summary: libgccjit.so.0: Cannot write-enable text segment:
                    Permission denied on NetBSD 9.1
           Product: gcc
           Version: 10.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: jit
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: swilde@sha-bang.de
  Target Milestone: ---

On NetBSD 9.1 i386 the Hello World example from
https://gcc.gnu.org/onlinedocs/jit/intro/tutorial01.html
fails with:

% ./tut01-hello-world
/usr/local/lib/libgccjit.so.0: text relocations
/usr/local/lib/libgccjit.so.0: Cannot write-enable text segment: Permission
denied

when security.pax.mprotect.global is enabled, which is the default on the
system.
When disabelin global memory protection (as root) with:

sysctl -w security.pax.mprotect.global=0

The example works (still emitting a warning:

% ./tut01-hello-world
/usr/local/lib/libgccjit.so.0: text relocations
hello world

Turning of security.pax.mprotect.global shouldn't be required for libgccjit
to work.

Also the warning "/usr/local/lib/libgccjit.so.0: text relocations" should
be prevented if possible.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
@ 2021-04-15 12:18 ` jakub at gcc dot gnu.org
  2021-04-15 13:21 ` swilde@sha-bang.de
                   ` (29 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-04-15 12:18 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
How did you build libgccjit.so.0?
Have you used --enable-host-shared during configure?

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
  2021-04-15 12:18 ` [Bug jit/100096] " jakub at gcc dot gnu.org
@ 2021-04-15 13:21 ` swilde@sha-bang.de
  2021-04-15 13:23 ` jakub at gcc dot gnu.org
                   ` (28 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2021-04-15 13:21 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #2 from Sascha Wilde <swilde@sha-bang.de> ---
> How did you build libgccjit.so.0?
> Have you used --enable-host-shared during configure?

Yes, AFAIK this is mandatory?

Here is the configuration I used:

../gcc-10.2.0/configure \
  --with-bugurl='https://github.com/jashandeep-sohi/libgccjit-pkg/issues' \
  --enable-shared \
  --enable-host-shared \
  --enable-checking=release \
  --enable-languages=jit \
  --disable-multilib \
  --disable-libssp \
  --disable-lto \
  --disable-libquadmath \
  --disable-liboffloadmic \
  --disable-libada \
  --disable-libsanitizer \
  --disable-libquadmath-support \
  --disable-libgomp \
  --disable-libvtv \
  --disable-libsanitizer \
  --with-gmp=/usr/local \
  --with-mpc=/usr/local \
  --with-mpfr=/usr/local

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
  2021-04-15 12:18 ` [Bug jit/100096] " jakub at gcc dot gnu.org
  2021-04-15 13:21 ` swilde@sha-bang.de
@ 2021-04-15 13:23 ` jakub at gcc dot gnu.org
  2021-04-15 13:30 ` swilde@sha-bang.de
                   ` (27 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-04-15 13:23 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So, how many text relocations do you see?
E.g. readelf -Wa libgccjit.so.0 output attached here would be useful.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (2 preceding siblings ...)
  2021-04-15 13:23 ` jakub at gcc dot gnu.org
@ 2021-04-15 13:30 ` swilde@sha-bang.de
  2021-04-15 13:32 ` swilde@sha-bang.de
                   ` (26 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2021-04-15 13:30 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #4 from Sascha Wilde <swilde@sha-bang.de> ---
Created attachment 50602
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50602&action=edit
Output of: readelf -Wa /usr/local/lib/libgccjit.so

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (3 preceding siblings ...)
  2021-04-15 13:30 ` swilde@sha-bang.de
@ 2021-04-15 13:32 ` swilde@sha-bang.de
  2021-04-15 13:36 ` swilde@sha-bang.de
                   ` (25 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2021-04-15 13:32 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #5 from Sascha Wilde <swilde@sha-bang.de> ---
(In reply to Jakub Jelinek from comment #3)
> So, how many text relocations do you see?
> E.g. readelf -Wa libgccjit.so.0 output attached here would be useful.

I attached the requested output (its nearly 9MiB uncompressed, so used bzip2 
to stay below the file size limit of 1000K)

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (4 preceding siblings ...)
  2021-04-15 13:32 ` swilde@sha-bang.de
@ 2021-04-15 13:36 ` swilde@sha-bang.de
  2021-04-15 13:38 ` schwab@linux-m68k.org
                   ` (24 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2021-04-15 13:36 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #6 from Sascha Wilde <swilde@sha-bang.de> ---
However, please note that
"Cannot write-enable text segment: Permission denied"
is the more pressing problem, as it prevents libgccjit to be used
on NetBSD with default security settings.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (5 preceding siblings ...)
  2021-04-15 13:36 ` swilde@sha-bang.de
@ 2021-04-15 13:38 ` schwab@linux-m68k.org
  2021-04-15 13:47 ` dmalcolm at gcc dot gnu.org
                   ` (23 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: schwab@linux-m68k.org @ 2021-04-15 13:38 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #7 from Andreas Schwab <schwab@linux-m68k.org> ---
That's just the consequence of text relocations.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (6 preceding siblings ...)
  2021-04-15 13:38 ` schwab@linux-m68k.org
@ 2021-04-15 13:47 ` dmalcolm at gcc dot gnu.org
  2021-04-15 14:03 ` jakub at gcc dot gnu.org
                   ` (22 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: dmalcolm at gcc dot gnu.org @ 2021-04-15 13:47 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #8 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Sascha Wilde from comment #6)
> However, please note that
> "Cannot write-enable text segment: Permission denied"
> is the more pressing problem, as it prevents libgccjit to be used
> on NetBSD with default security settings.

It would be good to know exactly where that error message is being emitted.

If you add:
  gcc_jit_context_set_logfile (ctxt, stderr, 0, 0);
to the test code (e.g. immediately after the call to gcc_jit_context_acquire),
libgccjit ought to spew out a copious amount of logging (see
https://gcc.gnu.org/onlinedocs/jit/internals/index.html#example-of-log-file)

Can you attach the log you get please?

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (7 preceding siblings ...)
  2021-04-15 13:47 ` dmalcolm at gcc dot gnu.org
@ 2021-04-15 14:03 ` jakub at gcc dot gnu.org
  2021-04-15 14:41 ` swilde@sha-bang.de
                   ` (21 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-04-15 14:03 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So I see 236 R_386_RELATIVE text relocations and 231 other text relocations.
Seems the compiler itself is built with -fpic/-fPIC, but some of the libraries
that are linked into it are not, e.g. libintl.a, at least parts of libgcc (the
dfp stuff), libbacktrace.
Perhaps
readelf -wi libgccjit.so.0 | grep DW_AT_producer
would make it clearer on what is and what is not built with -fpic/-fPIC.
On i686-linux I certainly can't reproduce this, there are no text relocations.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (8 preceding siblings ...)
  2021-04-15 14:03 ` jakub at gcc dot gnu.org
@ 2021-04-15 14:41 ` swilde@sha-bang.de
  2021-04-15 14:42 ` swilde@sha-bang.de
                   ` (20 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2021-04-15 14:41 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #10 from Sascha Wilde <swilde@sha-bang.de> ---
(In reply to David Malcolm from comment #8)
> It would be good to know exactly where that error message is being emitted.
> 
> If you add:
>   gcc_jit_context_set_logfile (ctxt, stderr, 0, 0);
> to the test code (e.g. immediately after the call to
> gcc_jit_context_acquire), libgccjit ought to spew out a copious amount of
> logging (see
> https://gcc.gnu.org/onlinedocs/jit/internals/index.html#example-of-log-file)
> 
> Can you attach the log you get please?

With security.pax.mprotect.global=1 it produces no extra output.
I'll attach the output produced when security.pax.mprotect.global is
disabled.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (9 preceding siblings ...)
  2021-04-15 14:41 ` swilde@sha-bang.de
@ 2021-04-15 14:42 ` swilde@sha-bang.de
  2021-04-15 14:58 ` swilde@sha-bang.de
                   ` (19 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2021-04-15 14:42 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #11 from Sascha Wilde <swilde@sha-bang.de> ---
Created attachment 50603
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50603&action=edit
tut01-hello-world log output

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (10 preceding siblings ...)
  2021-04-15 14:42 ` swilde@sha-bang.de
@ 2021-04-15 14:58 ` swilde@sha-bang.de
  2021-04-15 15:00 ` jakub at gcc dot gnu.org
                   ` (18 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2021-04-15 14:58 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #12 from Sascha Wilde <swilde@sha-bang.de> ---
(In reply to Jakub Jelinek from comment #9)
> Perhaps
> readelf -wi libgccjit.so.0 | grep DW_AT_producer
> would make it clearer on what is and what is not built with -fpic/-fPIC.

This runs quite long and only yields lines like:

    <d>   DW_AT_producer    : (indirect string, offset: 0x155c1): GNU C++14
10.2.0 -mtune=generic -march=i486 -g -O2 -fPIC -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables
    <30387>   DW_AT_producer    : (indirect string, offset: 0x155c1): GNU C++14
10.2.0 -mtune=generic -march=i486 -g -O2 -fPIC -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables
    <3ccf4>   DW_AT_producer    : (indirect string, offset: 0x155c1): GNU C++14
10.2.0 -mtune=generic -march=i486 -g -O2 -fPIC -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables

[...]

If this is really helpful to you, I'm fully willing to let it run through all 
the way and provide you with the complete output, of course.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (11 preceding siblings ...)
  2021-04-15 14:58 ` swilde@sha-bang.de
@ 2021-04-15 15:00 ` jakub at gcc dot gnu.org
  2021-04-15 15:08 ` jakub at gcc dot gnu.org
                   ` (17 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-04-15 15:00 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The important question is what TUs are compiled without -fPIC/-fpic, those with
those options are fine.
So perhaps
readelf -wi libgccjit.so.0 | grep DW_AT_producer | grep -v 'fPIC\|fpic'
?

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (12 preceding siblings ...)
  2021-04-15 15:00 ` jakub at gcc dot gnu.org
@ 2021-04-15 15:08 ` jakub at gcc dot gnu.org
  2021-04-15 16:13 ` swilde@sha-bang.de
                   ` (16 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-04-15 15:08 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Though, DW_AT_producer lines don't really provide the filename and comp_dir,
so guess what I need is better
readelf -wi libgccjit.so.0 | grep -A4 DW_AT_producer | bzip2 -9
output.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (13 preceding siblings ...)
  2021-04-15 15:08 ` jakub at gcc dot gnu.org
@ 2021-04-15 16:13 ` swilde@sha-bang.de
  2021-04-15 17:44 ` dmalcolm at gcc dot gnu.org
                   ` (15 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2021-04-15 16:13 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #15 from Sascha Wilde <swilde@sha-bang.de> ---
(In reply to Jakub Jelinek from comment #13)
> readelf -wi libgccjit.so.0 | grep DW_AT_producer | grep -v 'fPIC\|fpic'

FWIW, I had the command running for quite some while without spotting any
line not containing -fPIC -- but these might still come though...


(In reply to Jakub Jelinek from comment #14)
> Though, DW_AT_producer lines don't really provide the filename and comp_dir,
> so guess what I need is better
> readelf -wi libgccjit.so.0 | grep -A4 DW_AT_producer | bzip2 -9
> output.

Ill provide you with the output.  Please allow me some time, as this really 
runs _long_ on the system in question (a small Atom CPU N270).

I hope to provide the output tomorrow...

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (14 preceding siblings ...)
  2021-04-15 16:13 ` swilde@sha-bang.de
@ 2021-04-15 17:44 ` dmalcolm at gcc dot gnu.org
  2021-04-15 20:07 ` swilde@sha-bang.de
                   ` (14 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: dmalcolm at gcc dot gnu.org @ 2021-04-15 17:44 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #16 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Sascha Wilde from comment #10)
> (In reply to David Malcolm from comment #8)
> > It would be good to know exactly where that error message is being emitted.
> > 
> > If you add:
> >   gcc_jit_context_set_logfile (ctxt, stderr, 0, 0);
> > to the test code (e.g. immediately after the call to
> > gcc_jit_context_acquire), libgccjit ought to spew out a copious amount of
> > logging (see
> > https://gcc.gnu.org/onlinedocs/jit/internals/index.html#example-of-log-file)
> > 
> > Can you attach the log you get please?
> 
> With security.pax.mprotect.global=1 it produces no extra output.
> I'll attach the output produced when security.pax.mprotect.global is
> disabled.

Thanks!  I was wondering if the error message was:
  (a) due to a problem dynamically linking libgccjit into the process, or
  (b) a later problem with linking the code that libgccjit generates into the
process.

Given that there's no extra log output at all with the protection flag, it
sounds like it's (a) - though you may run into a similar problem with (b)
if/when (a) gets solved.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (15 preceding siblings ...)
  2021-04-15 17:44 ` dmalcolm at gcc dot gnu.org
@ 2021-04-15 20:07 ` swilde@sha-bang.de
  2021-04-16  9:37 ` swilde@sha-bang.de
                   ` (13 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2021-04-15 20:07 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #17 from Sascha Wilde <swilde@sha-bang.de> ---
(In reply to David Malcolm from comment #16)
> (In reply to Sascha Wilde from comment #10)
> > (In reply to David Malcolm from comment #8)
> > > It would be good to know exactly where that error message is being emitted.
> > > 
> > > If you add:
> > >   gcc_jit_context_set_logfile (ctxt, stderr, 0, 0);
> > > to the test code (e.g. immediately after the call to
> > > gcc_jit_context_acquire), libgccjit ought to spew out a copious amount of
> > > logging (see
> > > https://gcc.gnu.org/onlinedocs/jit/internals/index.html#example-of-log-file)
> > > 
> > > Can you attach the log you get please?
> > 
> > With security.pax.mprotect.global=1 it produces no extra output.
> > I'll attach the output produced when security.pax.mprotect.global is
> > disabled.
> 
> Thanks!  I was wondering if the error message was:
>   (a) due to a problem dynamically linking libgccjit into the process, or
>   (b) a later problem with linking the code that libgccjit generates into
> the process.
> 
> Given that there's no extra log output at all with the protection flag, it
> sounds like it's (a) - though you may run into a similar problem with (b)
> if/when (a) gets solved.

FWIW, the reason why I stumbled upon this problem is that I am testing
the native compiling GNU Emacs branch[0] on the NetBSD system.
(Which, by the way, can be build and works great once
security.pax.mprotect.global is disabled)

When security.pax.mprotect.global is enable the Emacs, linked with
libgccjit can not be started at all, failing with the same error as
the hello-world example.  So this matches your analysis that the
problem is triggered by dynamically linking libgccjit.

[0] https://akrl.sdf.org/gccemacs.html

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (16 preceding siblings ...)
  2021-04-15 20:07 ` swilde@sha-bang.de
@ 2021-04-16  9:37 ` swilde@sha-bang.de
  2021-04-16  9:38 ` swilde@sha-bang.de
                   ` (12 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2021-04-16  9:37 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #18 from Sascha Wilde <swilde@sha-bang.de> ---
Created attachment 50612
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50612&action=edit
Output of: readelf -wi libgccjit.so.0 | grep -A4 DW_AT_producer

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (17 preceding siblings ...)
  2021-04-16  9:37 ` swilde@sha-bang.de
@ 2021-04-16  9:38 ` swilde@sha-bang.de
  2021-04-16 11:28 ` jakub at gcc dot gnu.org
                   ` (11 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2021-04-16  9:38 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #19 from Sascha Wilde <swilde@sha-bang.de> ---
(In reply to Jakub Jelinek from comment #14)
> Though, DW_AT_producer lines don't really provide the filename and comp_dir,
> so guess what I need is better
> readelf -wi libgccjit.so.0 | grep -A4 DW_AT_producer | bzip2 -9
> output.

I now attached the requested output to the issue.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (18 preceding siblings ...)
  2021-04-16  9:38 ` swilde@sha-bang.de
@ 2021-04-16 11:28 ` jakub at gcc dot gnu.org
  2021-04-16 12:18 ` wilde@sha-bang.de
                   ` (10 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-04-16 11:28 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #20 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 50614
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50614&action=edit
gcc11-pr100096.patch

Thanks.  So, from your readelf -wi dump it seems it is only libintl.a that
doesn't have --enable-host-shared support.

So, can you please test this patch and see if all libgccjit.so* text
relocations are gone with that?

Can't test myself as on Linux libintl.a is never built - gettext is in the C
library.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (19 preceding siblings ...)
  2021-04-16 11:28 ` jakub at gcc dot gnu.org
@ 2021-04-16 12:18 ` wilde@sha-bang.de
  2021-04-16 12:25 ` jakub at gcc dot gnu.org
                   ` (9 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: wilde@sha-bang.de @ 2021-04-16 12:18 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #21 from wilde@sha-bang.de ---
"jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096
>
> --- Comment #20 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> Created attachment 50614
>   --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50614&action=edit
> gcc11-pr100096.patch
>
> Thanks.  So, from your readelf -wi dump it seems it is only libintl.a that
> doesn't have --enable-host-shared support.
>
> So, can you please test this patch and see if all libgccjit.so* text
> relocations are gone with that?

I will test the patch, given the hardware this will take some time
(I'll consider setting up a vm on a faster hardware).

The patch needs to be applied to gcc11, right?  If it were usable with
10.2.0 I could apply it to my existing build, which of course would be
much faster to rebuild...

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (20 preceding siblings ...)
  2021-04-16 12:18 ` wilde@sha-bang.de
@ 2021-04-16 12:25 ` jakub at gcc dot gnu.org
  2021-04-16 14:32 ` wilde@sha-bang.de
                   ` (8 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-04-16 12:25 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #22 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
It applies cleanly to gcc 10 too.  intl/ isn't really changing all that much...

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (21 preceding siblings ...)
  2021-04-16 12:25 ` jakub at gcc dot gnu.org
@ 2021-04-16 14:32 ` wilde@sha-bang.de
  2021-04-16 16:35 ` cvs-commit at gcc dot gnu.org
                   ` (7 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: wilde@sha-bang.de @ 2021-04-16 14:32 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #23 from wilde@sha-bang.de ---
"jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096
>
> --- Comment #22 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> It applies cleanly to gcc 10 too.  intl/ isn't really changing all that much...

I am very happy to confirm, that the patch completely solves the issue
for me.  The hello-world example as well as the native compiling GNU
Emacs both do now work perfectly fine and without any warnings with
security.pax.mprotect.global enabled.

Thanks a lot for the fast and friendly reply!

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (22 preceding siblings ...)
  2021-04-16 14:32 ` wilde@sha-bang.de
@ 2021-04-16 16:35 ` cvs-commit at gcc dot gnu.org
  2021-04-20  9:46 ` cvs-commit at gcc dot gnu.org
                   ` (6 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2021-04-16 16:35 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #24 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:4a1493f0603262a7dc1114d9827353e9810e63dc

commit r11-8225-g4a1493f0603262a7dc1114d9827353e9810e63dc
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Apr 16 18:32:27 2021 +0200

    intl: Add --enable-host-shared support [PR100096]

    As mentioned in the PR, building gcc with jit enabled and
    --enable-host-shared doesn't work on NetBSD/i?86, as libgccjit.so.0
    has text relocations.
    The r0-125846-g459260ecf8b420b029601a664cdb21c185268ecb changes
    added --enable-host-shared support to various libraries, but didn't
    add it to intl/ subdirectory; on Linux it isn't really needed, because
    all: all-no
    all-no: #nothing
    but on other OSes intl/libintl.a is built.

    The following patch makes sure it is built with -fPIC when
    --enable-host-shared is used.

    2021-04-16  Jakub Jelinek  <jakub@redhat.com>

            PR jit/100096
            * configure.ac: Add --enable-host-shared support.
            * Makefile.in: Update copyright.  Add @PICFLAG@ to CFLAGS.
            * configure: Regenerated.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (23 preceding siblings ...)
  2021-04-16 16:35 ` cvs-commit at gcc dot gnu.org
@ 2021-04-20  9:46 ` cvs-commit at gcc dot gnu.org
  2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org
                   ` (5 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2021-04-20  9:46 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #25 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:a11f31102706e33f66b60367d6863613ab3bd051

commit r10-9731-ga11f31102706e33f66b60367d6863613ab3bd051
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Apr 16 18:32:27 2021 +0200

    intl: Add --enable-host-shared support [PR100096]

    As mentioned in the PR, building gcc with jit enabled and
    --enable-host-shared doesn't work on NetBSD/i?86, as libgccjit.so.0
    has text relocations.
    The r0-125846-g459260ecf8b420b029601a664cdb21c185268ecb changes
    added --enable-host-shared support to various libraries, but didn't
    add it to intl/ subdirectory; on Linux it isn't really needed, because
    all: all-no
    all-no: #nothing
    but on other OSes intl/libintl.a is built.

    The following patch makes sure it is built with -fPIC when
    --enable-host-shared is used.

    2021-04-16  Jakub Jelinek  <jakub@redhat.com>

            PR jit/100096
            * configure.ac: Add --enable-host-shared support.
            * Makefile.in: Update copyright.  Add @PICFLAG@ to CFLAGS.
            * configure: Regenerated.

    (cherry picked from commit 4a1493f0603262a7dc1114d9827353e9810e63dc)

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (24 preceding siblings ...)
  2021-04-20  9:46 ` cvs-commit at gcc dot gnu.org
@ 2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org
  2021-04-22 16:53 ` cvs-commit at gcc dot gnu.org
                   ` (4 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2021-04-20 23:34 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #26 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:e173d85243b7732aa3ef29ebf7ecc6a54d21320c

commit r9-9449-ge173d85243b7732aa3ef29ebf7ecc6a54d21320c
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Apr 16 18:32:27 2021 +0200

    intl: Add --enable-host-shared support [PR100096]

    As mentioned in the PR, building gcc with jit enabled and
    --enable-host-shared doesn't work on NetBSD/i?86, as libgccjit.so.0
    has text relocations.
    The r0-125846-g459260ecf8b420b029601a664cdb21c185268ecb changes
    added --enable-host-shared support to various libraries, but didn't
    add it to intl/ subdirectory; on Linux it isn't really needed, because
    all: all-no
    all-no: #nothing
    but on other OSes intl/libintl.a is built.

    The following patch makes sure it is built with -fPIC when
    --enable-host-shared is used.

    2021-04-16  Jakub Jelinek  <jakub@redhat.com>

            PR jit/100096
            * configure.ac: Add --enable-host-shared support.
            * Makefile.in: Update copyright.  Add @PICFLAG@ to CFLAGS.
            * configure: Regenerated.

    (cherry picked from commit a11f31102706e33f66b60367d6863613ab3bd051)

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (25 preceding siblings ...)
  2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org
@ 2021-04-22 16:53 ` cvs-commit at gcc dot gnu.org
  2021-04-22 17:12 ` jakub at gcc dot gnu.org
                   ` (3 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2021-04-22 16:53 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #27 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:db80752e02b765dfc129892377aebf18bcb7fc8a

commit r8-10911-gdb80752e02b765dfc129892377aebf18bcb7fc8a
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Apr 16 18:32:27 2021 +0200

    intl: Add --enable-host-shared support [PR100096]

    As mentioned in the PR, building gcc with jit enabled and
    --enable-host-shared doesn't work on NetBSD/i?86, as libgccjit.so.0
    has text relocations.
    The r0-125846-g459260ecf8b420b029601a664cdb21c185268ecb changes
    added --enable-host-shared support to various libraries, but didn't
    add it to intl/ subdirectory; on Linux it isn't really needed, because
    all: all-no
    all-no: #nothing
    but on other OSes intl/libintl.a is built.

    The following patch makes sure it is built with -fPIC when
    --enable-host-shared is used.

    2021-04-16  Jakub Jelinek  <jakub@redhat.com>

            PR jit/100096
            * configure.ac: Add --enable-host-shared support.
            * Makefile.in: Update copyright.  Add @PICFLAG@ to CFLAGS.
            * configure: Regenerated.

    (cherry picked from commit a11f31102706e33f66b60367d6863613ab3bd051)

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (26 preceding siblings ...)
  2021-04-22 16:53 ` cvs-commit at gcc dot gnu.org
@ 2021-04-22 17:12 ` jakub at gcc dot gnu.org
  2021-09-11 14:29 ` pinskia at gcc dot gnu.org
                   ` (2 subsequent siblings)
  30 siblings, 0 replies; 32+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-04-22 17:12 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #28 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (27 preceding siblings ...)
  2021-04-22 17:12 ` jakub at gcc dot gnu.org
@ 2021-09-11 14:29 ` pinskia at gcc dot gnu.org
  2022-06-27  8:28 ` swilde@sha-bang.de
  2023-07-24  8:54 ` swilde@sha-bang.de
  30 siblings, 0 replies; 32+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-09-11 14:29 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |8.5

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (28 preceding siblings ...)
  2021-09-11 14:29 ` pinskia at gcc dot gnu.org
@ 2022-06-27  8:28 ` swilde@sha-bang.de
  2023-07-24  8:54 ` swilde@sha-bang.de
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2022-06-27  8:28 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

Sascha Wilde <swilde@sha-bang.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
             Status|RESOLVED                    |UNCONFIRMED
            Version|10.2.0                      |12.1.0

--- Comment #29 from Sascha Wilde <swilde@sha-bang.de> ---
Unfortunately the problem is still not fully resolved.
When bootstrapping the compiler (tested with 12.1 on NetBSD 9.2) libintl is
still build without -fPIC, however, when manually rebuilding libintl it is
build
correctly without any changes to the Makefile:

gmake BOOT_CFLAGS='-O' -j2 bootstrap   # wrong result, due to libintl w/o -fPIC
cd intl
gmake -j2 clean
gmake -j2  # builds a sane libintl with -fPIC
cd ..
gmake BOOT_CFLAGS='-O' -j2  # now results in a woring compiler and libgccjit.so

No idea why that is, but it's fully reproachable...

^ permalink raw reply	[flat|nested] 32+ messages in thread

* [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
  2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
                   ` (29 preceding siblings ...)
  2022-06-27  8:28 ` swilde@sha-bang.de
@ 2023-07-24  8:54 ` swilde@sha-bang.de
  30 siblings, 0 replies; 32+ messages in thread
From: swilde@sha-bang.de @ 2023-07-24  8:54 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096

--- Comment #30 from Sascha Wilde <swilde@sha-bang.de> ---
Anything else I should test?

^ permalink raw reply	[flat|nested] 32+ messages in thread

end of thread, other threads:[~2023-07-24  8:54 UTC | newest]

Thread overview: 32+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-15 11:14 [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 swilde@sha-bang.de
2021-04-15 12:18 ` [Bug jit/100096] " jakub at gcc dot gnu.org
2021-04-15 13:21 ` swilde@sha-bang.de
2021-04-15 13:23 ` jakub at gcc dot gnu.org
2021-04-15 13:30 ` swilde@sha-bang.de
2021-04-15 13:32 ` swilde@sha-bang.de
2021-04-15 13:36 ` swilde@sha-bang.de
2021-04-15 13:38 ` schwab@linux-m68k.org
2021-04-15 13:47 ` dmalcolm at gcc dot gnu.org
2021-04-15 14:03 ` jakub at gcc dot gnu.org
2021-04-15 14:41 ` swilde@sha-bang.de
2021-04-15 14:42 ` swilde@sha-bang.de
2021-04-15 14:58 ` swilde@sha-bang.de
2021-04-15 15:00 ` jakub at gcc dot gnu.org
2021-04-15 15:08 ` jakub at gcc dot gnu.org
2021-04-15 16:13 ` swilde@sha-bang.de
2021-04-15 17:44 ` dmalcolm at gcc dot gnu.org
2021-04-15 20:07 ` swilde@sha-bang.de
2021-04-16  9:37 ` swilde@sha-bang.de
2021-04-16  9:38 ` swilde@sha-bang.de
2021-04-16 11:28 ` jakub at gcc dot gnu.org
2021-04-16 12:18 ` wilde@sha-bang.de
2021-04-16 12:25 ` jakub at gcc dot gnu.org
2021-04-16 14:32 ` wilde@sha-bang.de
2021-04-16 16:35 ` cvs-commit at gcc dot gnu.org
2021-04-20  9:46 ` cvs-commit at gcc dot gnu.org
2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:53 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:12 ` jakub at gcc dot gnu.org
2021-09-11 14:29 ` pinskia at gcc dot gnu.org
2022-06-27  8:28 ` swilde@sha-bang.de
2023-07-24  8:54 ` swilde@sha-bang.de

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).