GNU help needed

Hello, My name is James Koren I'm a high school student looking for some assurance. I was looking for a compiler software for my Eclipse Neon 3 and came across you and your groups work. I want to use your program but I also want some clarification on what you guys are doing. I would like to know wh

Re: introduce --enable-mingw-full32 to default to --large-address-aware

On 10/05/2018 02:18 AM, Alexandre Oliva wrote: > Add a configure knob for mingw32 and 64 toolchains to default passing > --large-address-aware to the linker, when creating 32-bit binaries. > -Wl,--disable-large-address-aware can still reverse its effects. > > I've tested this with cross i686-pc-mi

Re: [PATCH, testsuite] memchr-1.c wide char and AIX

On Fri, Oct 5, 2018 at 5:47 PM Martin Sebor wrote: > > David, > > Attached is a patch to conditionalize the memchr-1.c test > to pass even with 2-byte wchar_t's. It also adds a compile > only test to verify memchr with -fnarrow-wchar. I verified > the changes on LE x86_64-linux and BE powerpc64-

Re: [PATCH, libgfortran] Remove recursion check

Hi Janne, The error handling functions can be called from a signal handler, so they need to be async-signal-safe. I didn't know that. How can this happen? Regards Thomas

[PATCH] Use gfc_charlen_type instead of int for string lenghts

This patch cleans up a few places where I noticed the code was still using int instead gfc_charlen_type for string lengths. Regtested on x86_64-pc-linux-gnu, committed as obvious. libgfortran/ChangeLog: 2018-10-06 Janne Blomqvist * io/unix.c (compare_file_filename): Use gfc_charlen_t

Re: [PATCH] i386: Use TImode for BLKmode values in 2 integer registers

On Sat, Oct 6, 2018 at 2:22 PM H.J. Lu wrote: > > On Sat, Oct 6, 2018 at 12:48 AM Uros Bizjak wrote: > > > > On Fri, Oct 5, 2018 at 1:43 PM H.J. Lu wrote: > > > > > > On Sat, Sep 29, 2018 at 11:02 AM Uros Bizjak wrote: > > > > > > > > On Sat, Sep 29, 2018 at 6:36 PM H.J. Lu wrote: > > > > > >

Re: [PATCH, libgfortran] Remove recursion check

On Sat, Oct 6, 2018 at 8:55 PM Thomas Koenig wrote: > Hi Jerry, > > > Agree it should be fixed. I would think a mutex lock should work. Lock, > > issue error message, unlock. Even if there is recursion, since there is > > at least one error somewhere, It should be OK to pause the world to > > iss

Re: [patch, fortran] Fix PR 86111, ICE on invalid

On 10/6/18 10:53 AM, Thomas Koenig wrote: Hello world, the attached patch fixes an ICE regression by issuing an error when a clever combination of array constructors ends up in gfc_arith_concat with mismatched types, before resultion has a chance to report the error. Regression-tested. OK for t

Re: [PATCH, libgfortran] Remove recursion check

Hi Jerry, Agree it should be fixed. I would think a mutex lock should work. Lock, issue error message, unlock. Even if there is recursion, since there is at least one error somewhere, It should be OK to pause the world to issue the error, and come back and finish. AS I think about it, maybe o

[patch, fortran] Fix PR 86111, ICE on invalid

Hello world, the attached patch fixes an ICE regression by issuing an error when a clever combination of array constructors ends up in gfc_arith_concat with mismatched types, before resultion has a chance to report the error. Regression-tested. OK for trunk? Regards Thomas 2018-10-06

[wwwdocs] readings.html - remove stale linke "Debugging/object info" (to sgi.com)

With HPE "integrating" SGI, ftp.sgi.com has gone away without a replacement I could find, and I've also failed to find a potentially new home for this document. So I had to go ahead with the patch below; committed. Gerald Index: htdocs/readings.html ==

Re: [PATCH, libgfortran] Remove recursion check

On 10/6/18 10:00 AM, Janne Blomqvist wrote: On Mon, Sep 24, 2018 at 10:18 PM Janne Blomqvist wrote: On Mon, Sep 24, 2018 at 7:48 PM Thomas Koenig wrote: Hi Janne, libgfortran has a recursion check in the error handling paths. This works by checking the value of a static variable, and if

Re: [PATCH, libgfortran] Remove recursion check

On Mon, Sep 24, 2018 at 10:18 PM Janne Blomqvist wrote: > On Mon, Sep 24, 2018 at 7:48 PM Thomas Koenig > wrote: > >> Hi Janne, >> >> > libgfortran has a recursion check in the error handling paths. This >> > works by checking the value of a static variable, and if it matches, >> > aborting imm

Re: [PATCH] i386: Use TImode for BLKmode values in 2 integer registers

On Sat, Oct 6, 2018 at 12:48 AM Uros Bizjak wrote: > > On Fri, Oct 5, 2018 at 1:43 PM H.J. Lu wrote: > > > > On Sat, Sep 29, 2018 at 11:02 AM Uros Bizjak wrote: > > > > > > On Sat, Sep 29, 2018 at 6:36 PM H.J. Lu wrote: > > > > > > > > When passing and returning BLKmode values in 2 integer regi

[patch, committed] Fix PR 84640

Hi, I just committed the fix below as obvious and simple. No test case because the problem was only visible in with an instrumented compiler. Regards Thomas 2018-10-06 Thomas Koenig PR fortran/84640 * simplify.c (gfc_simplify_cshift): Extend size of hs_ex and ss_ex

Re: [PATCH] i386: Use TImode for BLKmode values in 2 integer registers

On Fri, Oct 5, 2018 at 1:43 PM H.J. Lu wrote: > > On Sat, Sep 29, 2018 at 11:02 AM Uros Bizjak wrote: > > > > On Sat, Sep 29, 2018 at 6:36 PM H.J. Lu wrote: > > > > > > When passing and returning BLKmode values in 2 integer registers, use > > > 1 TImode register instead of 2 DImode registers. Ot