I was able to reproduce this with GCC 9.0.1 20190430 as well.
It appears that adding -MD to the PCH build sometimes causes the "deps"
data in the PCH file to be empty, but this is never noticed unless you
use the -fpch-deps option on the source compile line: if you don't do
this then nothing in GC
On Tue, Apr 30, 2019 at 03:48:02PM -0600, Jeff Law wrote:
> On 4/30/19 11:24 AM, Matthew Malcomson wrote:
> > That was why I ended up suggesting multiple notes -- it's currently
> > trying to satisfy more than one criteria and they're not quite compatible.
> Well, we obviously have to keep arg set
On Wed, May 01, 2019 at 02:48:30PM -0400, Arvind Sankar wrote:
> On Wed, May 01, 2019 at 02:36:10PM -0400, Carlos O'Donell wrote:
> > On 5/1/19 2:24 PM, Arvind Sankar wrote:
> > > gcc 9 when configured for fortran installs ISO_Fortran_Binding.h in
> > > gfor_cdir =
> > > $(libdir)/gcc/$(target_a
On Wed, May 01, 2019 at 02:36:10PM -0400, Carlos O'Donell wrote:
> On 5/1/19 2:24 PM, Arvind Sankar wrote:
> > gcc 9 when configured for fortran installs ISO_Fortran_Binding.h in
> > gfor_cdir =
> > $(libdir)/gcc/$(target_alias)/$(gcc_version)$(MULTISUBDIR)/include
> > For x86_64's 32-bit arch
On 5/1/19 2:24 PM, Arvind Sankar wrote:
gcc 9 when configured for fortran installs ISO_Fortran_Binding.h in
gfor_cdir =
$(libdir)/gcc/$(target_alias)/$(gcc_version)$(MULTISUBDIR)/include
For x86_64's 32-bit architecture support, this creates a subdirectory named
'include'
inside $(libsu
gcc 9 when configured for fortran installs ISO_Fortran_Binding.h in
gfor_cdir =
$(libdir)/gcc/$(target_alias)/$(gcc_version)$(MULTISUBDIR)/include
For x86_64's 32-bit architecture support, this creates a subdirectory named
'include'
inside $(libsubdir)/32 which didn't use to exist in gcc
gcc 9 when configured for fortran installs ISO_Fortran_Binding.h in
gfor_cdir =
$(libdir)/gcc/$(target_alias)/$(gcc_version)$(MULTISUBDIR)/include
For x86_64's 32-bit architecture support, this creates a subdirectory named
'include'
inside $(libsubdir)/32 which didn't use to exist in gcc
On Wed, 2019-05-01 at 09:35 -0400, Paul Smith wrote:
> > Unfortunately my GCC is heavily optimized and stripped so backtraces
> > are useless. I will generate a debuggable GCC and see if I can get
> > more info on the ICE.
>
> I have created a GCC with debug enabled so I'll see what I find.
I wa
Hi Jakub,
> On 30 Apr 2019, at 14:12, Jakub Jelinek wrote:
>
> The second release candidate for GCC 9.1 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/9.0.1-RC-20190430/
> ftp://gcc.gnu.org/pub/gcc/snapshots/9.0.1-RC-20190430
>
> and shortly its mirrors. It has been generated fro
On 4/30/19 8:12 AM, Jakub Jelinek wrote:
The second release candidate for GCC 9.1 is available from
https://gcc.gnu.org/pub/gcc/snapshots/9.0.1-RC-20190430/
ftp://gcc.gnu.org/pub/gcc/snapshots/9.0.1-RC-20190430
and shortly its mirrors. It has been generated from SVN revision 270689.
I hav
On Tue, 2019-04-30 at 09:43 -0400, Paul Smith wrote:
> Here's the thing: I added the "-MD -MF foo.d" options to the PCH file
> compile (I wanted to get a manifest of which files were included in the
> PCH file). Without those options I cannot reproduce this at all (in a
> number of tries). With t
On 30/04/19 22:48, Jeff Law wrote:
> On 4/30/19 11:24 AM, Matthew Malcomson wrote:
>> On 30/04/19 18:01, Jeff Law wrote:
>>> On 4/30/19 10:48 AM, Matthew Malcomson wrote:
Hi Jeff,
On 30/04/19 16:29, Jeff Law wrote:
> On 1/4/19 9:03 AM, Matthew Malcomson wrote:
>> Hi there,
>>
12 matches
Mail list logo
