Hi Harald,
On 18.08.21 23:01, Harald Anlauf wrote:
Von: "Tobias Burnus"
Note, however, that gfc_simplify_len still won't handle neither
deferred strings nor their substrings.
Obviously, nonsubstrings cannot be simplified but I do not
see why len(str(1:2)) cannot or should not be simplified.
I have applied the patches locally (take care to restore the tabs ;)).
Should I now commit these changes or is there a more formal procedure
involved?
Regards,
Arjen
Op do 19 aug. 2021 om 08:59 schreef Arjen Markus :
> Hi Steve,
>
> I am willing to take up this challenge ;), as well as the patc
Arjen,
If this is your first go around with patching gfortran,
I'll suggest running the testsuite (if you haven't, see
step 5. below; if you have see step 6.). I suspect you
already know much of what I enumerate below, but it may
help others.
With a bug report, the workflow for me is/was
1. Che
On 7/27/21 5:07 AM, Tobias Burnus wrote:
Hi Sandra, hi Thomas, hi all,
@Thomas K: Comments about the following - and of course to the
testsuite itself - are highly welcome.
In my opinion, the testsuite LGTM and can be committed.
@Sandra:
- Thoughts on the directory name? (cf. below)
- Give oth
Hi Tobias,
> I am inclined to say that the Intel compiler has a bug by not
> accepting it – but as written before, I regard sub-string length
> (esp. with const expr) inquiries as an odd corner case which
> is unlikely to occur in real-world code.
ok.
> Still does not work – or rather: ...%t(:)(
Hi,
A while ago had a report of build failure against a Darwin branch on
the latest OS release. This was because (temporarily) the symlink
from libm.dylib => libSystem.dylib had been removed/omitted.
libm is not needed on Darwin, and should not be added unconditionally
even if that is (mostly) h
On Thu, Aug 19, 2021 at 12:12 PM Harald Anlauf via Gcc-patches
wrote:
>
> Hi Tobias,
>
> > I am inclined to say that the Intel compiler has a bug by not
> > accepting it – but as written before, I regard sub-string length
> > (esp. with const expr) inquiries as an odd corner case which
> > is unli
I've backported several patches having to do with Fortran/C
interoperability from mainline to the OG11 branch. See attached log for
details.
-Sandra
commit d554155c07771935778f557e9ef649cc3624d1ce
Author: Sandra Loosemore
Date: Wed Aug 11 19:24:17 2021 -0700
Fortran: Fix c_float128 and
Hi Steve,
thanks for this detailed workflow. I am familiar enough with git to know
that there are myriads of procedures possible ;). Like you said, the first
three steps have been done. I will get working on step 4 and work my way
down the list.
Regards,
Arjen
Op do 19 aug. 2021 om 18:23 schree
Feel free to ask questions. I forgot to point to
the contributing page
https://gcc.gnu.org/contribute.html
At one time, you need to assign copyright to the FSF.
That is no longer required. Scan the above page for
details.
--
steve
On Fri, Aug 20, 2021 at 08:36:42AM +0200, Arjen Markus wrote:
Hi!
> Gesendet: Freitag, 20. August 2021 um 02:21 Uhr
> Von: "H.J. Lu"
> This may have broken bootstrap on 32-bit hosts:
>
> https://gcc.gnu.org/pipermail/gcc-regression/2021-August/075209.html
I do not understand the error message:
../../src-master/gcc/fortran/simplify.c: In function ‘bool
Yes, I already had arranged for that copyright one and a half years ago,
but my first attempts failed (learning curve, real life getting in the way
etc.)
Op vr 20 aug. 2021 om 08:47 schreef Steve Kargl <
s...@troutmask.apl.washington.edu>:
> Feel free to ask questions. I forgot to point to
> the
12 matches
Mail list logo
