https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89830
Thomas Koenig changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89830
--- Comment #9 from Thomas Koenig ---
Rather than create a new compiler option, it is possible to compile to an
assembler
file using -S, look for .ascii „bar/foo.f90\0“ and replace with a sed or perl
script
according to your specification (for ex
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89830
--- Comment #8 from Steve Kargl ---
On Wed, Mar 27, 2019 at 02:55:56PM +, dominiq at lps dot ens.fr wrote:
>
> AFAIU this PR reports two issues with no or little connection with REPEAT.
>
Yes, and we have already agreed to close this one bec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89830
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89830
--- Comment #6 from Steve Kargl ---
On Tue, Mar 26, 2019 at 06:32:21PM +, zbeekman at gmail dot com wrote:
> Also, given that my reproducer code was dumb, should we close this an open a
> new issue to track the paths getting embedded? Or sho
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89830
--- Comment #5 from Zaak ---
Sorry about the bad reproducer code (name conflict).
To create reproducible builds one must be able to strip or at least map source
file references from the source/build directory to something more generic or
univers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89830
--- Comment #4 from Steve Kargl ---
On Tue, Mar 26, 2019 at 05:59:08PM +, tkoenig at gcc dot gnu.org wrote:
>
> --- Comment #3 from Thomas Koenig ---
> (In reply to Zaak from comment #0)
>
> > Furthermore, there is an error message embedde
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89830
Thomas Koenig changed:
What|Removed |Added
CC||tkoenig at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89830
--- Comment #2 from kargl at gcc dot gnu.org ---
(In reply to Zaak from comment #0)
> When compiled, even with the `-fno-working-directory` flag, the object file
> still contains references to the full path to the source file:
>
> ```
> $ strin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89830
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
--- C
10 matches
Mail list logo