[PATCH] PR fortran/90297 -- Remove code with no functional effect

The patch is fairly self-explanatory. OK to commit? 2019-10-11 Steven G. Kargl PR fortran/90297 * resolve.c (resolve_typebound_function): Remove code with no functional effect. -- Steve Index: gcc/fortran/resolve.c

Re: [PATCH][ARM] Switch to default sched pressure algorithm

On Fri, Oct 11, 2019 at 6:19 PM Wilco Dijkstra wrote: > > Hi Ramana, > > > Can you see what happens with the Cortex-A8 or Cortex-A9 schedulers to > > spread the range across some v7-a CPUs as well ? While they aren't that > > popular today I > > would suggest you look at them because the defaults

Re: [PATCH][ARM] Switch to default sched pressure algorithm

On Fri, Oct 11, 2019 at 10:42 PM Wilco Dijkstra wrote: > > Hi, > > > the defaults for v7-a are still to use the > > Cortex-A8 scheduler > > I missed that part, but that's a serious bug btw - Cortex-A8 is 15 years old > now so > way beyond obsolete. Even Cortex-A53 is ancient now, but it has an

Go patch commited: Mangle dots in pkgpath

The Go frontend needs to mangle dots to avoid problems with -fgo-pkgpath=a.0. That will confuse the name mangling, which assumes that names entering the mangling cannot contain arbitrary dot characters. We don't need to mangle other characters; go_encode_id will handle them. This patch fixes the

[PATCH] rs6000: -flto forgets 'no-vsx' function attributes (PR target/70010)

Hi, As expected in the PR, when a function is marked with no-vsx, we would assume user has good reason to disable VSX code generation for the function. To avoid VSX code generation, this function should not be inlined into VSX function. In previous implementation, function with non-vsx is trea

[PATCH] PR fortran/91513 -- Fix poorly worded error message

In PR fortran/91513, Damian Rouson points out that the Fortran does contain the words "impure variable". Damian and I spent an afternoon together a few weeks ago where I gave Damian a world wind view of how I see gcc/fortran and go about debugging problems. Damian and I both have full schedules,

Re: [PATCH] PR fortran/91513 -- Fix poorly worded error message

On Fri, Oct 11, 2019 at 09:56:15PM -0700, Steve Kargl wrote: > In PR fortran/91513, Damian Rouson points out that the Fortran > does contain the words "impure variable". Geez. That is a messed up sentence. In PR fortran/91513, Damian Rouson points out that the Fortran *standard* does *not* contai

<    1   2