[Bug other/35014] Libgfortran.a (downloaded) is not PIC compiled...

2024-03-17 Thread a.shahmoradi at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35014

--- Comment #16 from Amir Shahmoradi  ---
A new optional flag could be a viable (and in my opinion, very good) solution.
Unfortunately, I do not have the expertise and experience with gfortran
internals to propose and implement a patch for such an option.

[Bug other/35014] Libgfortran.a (downloaded) is not PIC compiled...

2024-03-16 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35014

Iain Sandoe  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |---

--- Comment #15 from Iain Sandoe  ---
(In reply to Amir Shahmoradi from comment #14)
> It's not a bug but a popular requested feature. See, for example, the
> discussion here:
> https://fortran-lang.discourse.group/t/distribute-shared-libraries-or-not/
> 7532/1

OK - I will reopen - but really someone needs to propose a patch - otherwise
releases just go by.

> Are there any downsides to distributing PIC-enabled `libgfortran.a` on all
> platforms?

yes. For platforms that support non-pic user-space code (e.g. Linux) then this
would produce a performance penalty (since the PIC code is typically slower)

> For consistency, if this is the default behavior on macOS, it should be the
> default on all platforms.

I doubt that would be a general agreement.

If a given distribution (or use-case) needs the PIC version [and I can totally
see why that would be the case for embedding it in a plugin) - then perhaps a
suitable solution would be to introduce a specific configuration flag like
"--enable-pic-runtimes" or "--enable-pic-libgfortran"

[Bug other/35014] Libgfortran.a (downloaded) is not PIC compiled...

2024-03-16 Thread a.shahmoradi at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35014

--- Comment #14 from Amir Shahmoradi  ---
It's not a bug but a popular requested feature. See, for example, the
discussion here:
https://fortran-lang.discourse.group/t/distribute-shared-libraries-or-not/7532/1
Are there any downsides to distributing PIC-enabled `libgfortran.a` on all
platforms?
For consistency, if this is the default behavior on macOS, it should be the
default on all platforms.

[Bug other/35014] Libgfortran.a (downloaded) is not PIC compiled...

2024-03-16 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35014

Iain Sandoe  changed:

   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #13 from Iain Sandoe  ---
no feedback since 2021.

[Bug other/35014] Libgfortran.a (downloaded) is not PIC compiled...

2021-05-31 Thread dominiq at lps dot ens.fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35014

Dominique d'Humieres  changed:

   What|Removed |Added

  Component|libfortran  |other

--- Comment #12 from Dominique d'Humieres  ---
No feedback. This is not a libgfortran bug, moving.