Re: [Mingw-w64-public] Internal compiler error specific to MinGW when using -fstack-clash-protection and __attribute__((noreturn))

2023-02-04 Thread Christian Franke

LIU Hao wrote:

在 2023-02-04 20:51, Théo Cavignac 写道:

Sorry, I misclicked and sent an half written mail.

So as I tried to expose, I am using MinGW with following configuration:




This looks like a GCC issue. Reported here: 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108673




Workaround: -fno-ipa-pure-const (see bugzilla entry).



___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] Internal compiler error specific to MinGW when using -fstack-clash-protection and __attribute__((noreturn))

2023-02-04 Thread LIU Hao

在 2023-02-04 20:51, Théo Cavignac 写道:

Sorry, I misclicked and sent an half written mail.

So as I tried to expose, I am using MinGW with following configuration:




This looks like a GCC issue. Reported here: 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108673


--
Best regards,
LIU Hao



OpenPGP_signature
Description: OpenPGP digital signature
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] Internal compiler error specific to MinGW when using -fstack-clash-protection and __attribute__((noreturn))

2023-02-04 Thread Théo Cavignac

Sorry, I misclicked and sent an half written mail.

So as I tried to expose, I am using MinGW with following configuration:

   Using built-in specs.
   COLLECT_GCC=x86_64-w64-mingw32-gcc
   COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-w64-mingw32/12.2.0/lto-wrapper
   Target: x86_64-w64-mingw32
   Configured with: /build/mingw-w64-gcc/src/gcc/configure
   --prefix=/usr --libexecdir=/usr/lib --target=x86_64-w64-mingw32
   --with-bugurl=https://bugs.archlinux.org/
   --enable-languages=c,lto,c++,ada,objc,obj-c++,fortran
   --enable-shared --enable-static --enable-threads=posix
   --enable-fully-dynamic-string --enable-libstdcxx-time=yes
   --enable-libstdcxx-filesystem-ts=yes --with-system-zlib
   --enable-cloog-backend=isl --enable-lto --enable-libgomp
   --disable-multilib --enable-checking=release
   --disable-sjlj-exceptions --with-dwarf2
   Thread model: posix
   Supported LTO compression algorithms: zlib zstd
   gcc version 12.2.0 (GCC)

And comparing to GCC configured like that:

   Using built-in specs.
   COLLECT_GCC=gcc
   COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/12.2.0/lto-wrapper
   Target: x86_64-pc-linux-gnu
   Configured with: /build/gcc/src/gcc/configure
   --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d
   --enable-bootstrap --prefix=/usr --libdir=/usr/lib
   --libexecdir=/usr/lib --mandir=/usr/share/man
   --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/
   --with-build-config=bootstrap-lto --with-linker-hash-style=gnu
   --with-system-zlib --enable-__cxa_atexit --enable-cet=auto
   --enable-checking=release --enable-clocale=gnu --enable-default-pie
   --enable-default-ssp --enable-gnu-indirect-function
   --enable-gnu-unique-object --enable-libstdcxx-backtrace
   --enable-link-serialization=1 --enable-linker-build-id --enable-lto
   --enable-multilib --enable-plugin --enable-shared
   --enable-threads=posix --disable-libssp --disable-libstdcxx-pch
   --disable-werror
   Thread model: posix
   Supported LTO compression algorithms: zlib zstd
   gcc version 12.2.0 (GCC)

And when compiling this minimal snippet:

   /*
  /usr/bin/x86_64-w64-mingw32-gcc \
    -O2 -fstack-clash-protection -c \
    -freport-bug \
    -o f.o f.c
 */
   void exit(int) __attribute__((noreturn));

   void foo(int p) {
  exit(p);
   }

Everything work as expected with GCC but MinGW gives this error:

   during RTL pass: final
   f.c: In function 'foo':
   f.c:11:1: internal compiler error: in seh_emit_stackalloc, at
   config/i386/winnt.cc:1055
   11 | }
  | ^
   0x19c77e7 internal_error(char const*, ...)
    ???:0
   0x6738cc fancy_abort(char const*, int, char const*)
    ???:0
   0xfc88e8 i386_pe_seh_unwind_emit(_IO_FILE*, rtx_insn*)
    ???:0
   0x8da73b final_scan_insn(rtx_insn*, _IO_FILE*, int, int, int*)
    ???:0

I honestly don't understand much of the internals of MinGW or GCC so I 
am absolutely not able to dig deeper into this, but I still think this 
is worth investigating if someone more skilled is willing to do it.


As for the use case, the particular set of flag comes from systematic 
configuration of packages compiled for Arch Linux and I found it while 
trying to use MinGW to cross compile some Nim code.


Best regards,

Théo



___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


[Mingw-w64-public] Internal compiler error specific to MinGW when using -fstack-clash-protection and __attribute__((noreturn))

2023-02-04 Thread Théo Cavignac

Hello,

As implied by the subject I isolated an internal compiler error that is 
specific to MinGW (stock GCC



Minimal code

   /*
  /usr/bin/x86_64-w64-mingw32-gcc \
    -O2 -fstack-clash-protection -c \
    -freport-bug \
    -o f.o f.c
 */
   void exit(int) __attribute__((noreturn));

   void foo(int p) {
  exit(p);
   }


Result:

   during RTL pass: final
   f.c: In function 'foo':
   f.c:11:1: internal compiler error: in seh_emit_stackalloc, at
   config/i386/winnt.cc:1055
   11 | }
  | ^
   0x19c77e7 internal_error(char const*, ...)
    ???:0
   0x6738cc fancy_abort(char const*, int, char const*)
    ???:0
   0xfc88e8 i386_pe_seh_unwind_emit(_IO_FILE*, rtx_insn*)
    ???:0
   0x8da73b final_scan_insn(rtx_insn*, _IO_FILE*, int, int, int*)
    ???:0



___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] Internal compiler error building mingw-w64-crt (default msvcrt is ucrt)

2021-11-09 Thread Kacvinsky, Tom
Weird, running make without the -j option magically "fixed" the error.  Not 
sure why.

From: Kacvinsky, Tom
Sent: Tuesday, November 9, 2021 6:32 PM
To: mingw-w64-public@lists.sourceforge.net
Subject: Internal compiler error building mingw-w64-crt (default msvcrt is ucrt)

I am building (once again) a GCC with UCRT support, this time using the UCRT64 
tool chain
that I was able to install today.  I am using master of the mingw-w64 git repo, 
freshly updated
today, but have a problem building the CRT libraries:

D:/DEV/mingw-w64-gcc-11.2.0-ucrt-1/x86_64-w64-mingw32/include/psdk_inc/intrin-impl.h:65:9:
 internal compiler error: Segmentation fault

Configure of mingw-64-headers is

configure --prefix=/d/DEV/mingw-w64-gcc-11.2.0-ucrt-1/x86_64-w64-mingw32  
--with-default-msvcrt=ucrt

Configure of mingw-w64-crt is

configure --prefix=/d/DEV/mingw-w64-gcc-11.2.0-ucrt-1/x86_64-w64-mingw32  
--with-default-msvcrt=ucrt

Compiler in use is

$ which gcc
/ucrt64/bin/gcc

$ gcc --version
gcc.exe (Rev1, Built by MSYS2 project) 11.2.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Is there a source package available (base UCRT64 GCC 11.2 + MinGW-w64 patches) 
that I
can use (in some sense, a debug package for GCC) so I can run this through a 
debugger and
see why there is a segmentation fault?

I should  add that this happens even with the v9.0.0 tag of the mingw-w64 clone 
I have.

In case anyone is curious as to why I keep bringing this topic up, it's because 
now I am trying
to work out some stuff with SEH  handling cross tool chain (MSVC for C/C++ and 
GCC for Ada).

Tom

___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


[Mingw-w64-public] Internal compiler error building mingw-w64-crt (default msvcrt is ucrt)

2021-11-09 Thread Kacvinsky, Tom
I am building (once again) a GCC with UCRT support, this time using the UCRT64 
tool chain
that I was able to install today.  I am using master of the mingw-w64 git repo, 
freshly updated
today, but have a problem building the CRT libraries:

D:/DEV/mingw-w64-gcc-11.2.0-ucrt-1/x86_64-w64-mingw32/include/psdk_inc/intrin-impl.h:65:9:
 internal compiler error: Segmentation fault

Configure of mingw-64-headers is

configure --prefix=/d/DEV/mingw-w64-gcc-11.2.0-ucrt-1/x86_64-w64-mingw32  
--with-default-msvcrt=ucrt

Configure of mingw-w64-crt is

configure --prefix=/d/DEV/mingw-w64-gcc-11.2.0-ucrt-1/x86_64-w64-mingw32  
--with-default-msvcrt=ucrt

Compiler in use is

$ which gcc
/ucrt64/bin/gcc

$ gcc --version
gcc.exe (Rev1, Built by MSYS2 project) 11.2.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Is there a source package available (base UCRT64 GCC 11.2 + MinGW-w64 patches) 
that I
can use (in some sense, a debug package for GCC) so I can run this through a 
debugger and
see why there is a segmentation fault?

I should  add that this happens even with the v9.0.0 tag of the mingw-w64 clone 
I have.

In case anyone is curious as to why I keep bringing this topic up, it's because 
now I am trying
to work out some stuff with SEH  handling cross tool chain (MSVC for C/C++ and 
GCC for Ada).

Tom

___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


[Mingw-w64-public] internal compiler error

2018-01-18 Thread Matt Sexton via Mingw-w64-public
Hello,

x86_64-w64-mingw32-gcc from the mingw64-gcc-7.2.0-1.fc27.x86_64 package on
Fedora 27 is reporting the following error in compiling some of our code:

internal compiler error: in get_constraint_for_ptr_offset, at
tree-ssa-structalias.c:3155

Is this the right place to ask about the bug?

Assuming so, here is some more information.  We see this on Fedora 27 with
the standard package:

$ x86_64-w64-mingw32-gcc -v
Using built-in specs.
COLLECT_GCC=x86_64-w64-mingw32-gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-w64-mingw32/7.2.0/lto-wrapper
Target: x86_64-w64-mingw32
Configured with: ../configure --prefix=/usr --bindir=/usr/bin
--includedir=/usr/include --mandir=/usr/share/man --infodir=/usr/share/info
--datadir=/usr/share --build=x86_64-redhat-linux-gnu
--host=x86_64-redhat-linux-gnu --with-gnu-as --with-gnu-ld --verbose
--without-newlib --disable-multilib --disable-plugin --with-system-zlib
--disable-nls --without-included-gettext --disable-win32-registry
--enable-languages=c,c++,objc,obj-c++,fortran --with-bugurl=
http://bugzilla.redhat.com/bugzilla --with-cloog --enable-threads=posix
--enable-libgomp --target=x86_64-w64-mingw32
--with-sysroot=/usr/x86_64-w64-mingw32/sys-root
--with-gxx-include-dir=/usr/x86_64-w64-mingw32/sys-root/mingw/include/c++
Thread model: posix
gcc version 7.2.0 20170814 (Fedora MinGW 7.2.0-1.fc27) (GCC)

We also see the same issue on Fedora 25

$ x86_64-w64-mingw32-gcc -v
Using built-in specs.
COLLECT_GCC=x86_64-w64-mingw32-gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-w64-mingw32/6.4.0/lto-wrapper
Target: x86_64-w64-mingw32
Configured with: ../configure --prefix=/usr --bindir=/usr/bin
--includedir=/usr/include --mandir=/usr/share/man --infodir=/usr/share/info
--datadir=/usr/share --build=x86_64-redhat-linux-gnu
--host=x86_64-redhat-linux-gnu --with-gnu-as --with-gnu-ld --verbose
--without-newlib --disable-multilib --disable-plugin --with-system-zlib
--disable-nls --without-included-gettext --disable-win32-registry
--enable-languages=c,c++,objc,obj-c++,fortran --with-bugurl=
http://bugzilla.redhat.com/bugzilla --with-cloog --enable-threads=posix
--enable-libgomp --target=x86_64-w64-mingw32
--with-sysroot=/usr/x86_64-w64-mingw32/sys-root
--with-gxx-include-dir=/usr/x86_64-w64-mingw32/sys-root/mingw/include/c++
Thread model: posix
gcc version 6.4.0 20170704 (Fedora MinGW 6.4.0-1.fc25) (GCC)

We do not see the issue on Fedora 21:

$ x86_64-w64-mingw32-gcc -v
Using built-in specs.
COLLECT_GCC=x86_64-w64-mingw32-gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-w64-mingw32/4.9.2/lto-wrapper
Target: x86_64-w64-mingw32
Configured with: ../configure --prefix=/usr --bindir=/usr/bin
--includedir=/usr/include --mandir=/usr/share/man --infodir=/usr/share/info
--datadir=/usr/share --build=x86_64-redhat-linux-gnu
--host=x86_64-redhat-linux-gnu --with-gnu-as --with-gnu-ld --verbose
--without-newlib --disable-multilib --disable-plugin --with-system-zlib
--disable-nls --without-included-gettext --disable-win32-registry
--enable-languages=c,c++,objc,obj-c++,fortran --with-bugurl=
http://bugzilla.redhat.com/bugzilla --with-cloog --enable-threads=posix
--enable-libgomp --target=x86_64-w64-mingw32
--with-sysroot=/usr/x86_64-w64-mingw32/sys-root
--with-gxx-include-dir=/usr/x86_64-w64-mingw32/sys-root/mingw/include/c++
Thread model: posix
gcc version 4.9.2 20141030 (Fedora MinGW 4.9.2-1.fc21) (GCC)

We only see the issue when optimization is enabled.

When building the same code natively using gcc on CentOS 6 and 7 and Fedora
21, 26, and 27, we see no such error.  I do not have a pared-down,
stand-alone case that reproduces the issue, nor do I have a clear
correlation with any particular code pattern.  Could anyone shed any light
on what this error means, so that I might have a better chance of working
around it?

Thank you,
Matt
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] internal compiler error 4.9.2

2016-04-01 Thread Victor Bombi
I am not sure if it has been seen so I confirm again that internal error 
persists with 4.9.3

victor bombi

- Original Message - 
From: "Victor Bombi" <son...@telefonica.net>
To: <mingw-w64-public@lists.sourceforge.net>
Sent: Monday, March 14, 2016 7:31 PM
Subject: Re: [Mingw-w64-public] internal compiler error 4.9.2


> The same intenal error is happening
>
> - Original Message - 
> From: "niXman" <i.nix...@autistici.org>
> To: <mingw-w64-public@lists.sourceforge.net>
> Sent: Thursday, March 03, 2016 5:45 PM
> Subject: Re: [Mingw-w64-public] internal compiler error 4.9.2
>
>
>>
>>> I have got an internal compiler error with mingw-w64 posi-dwarf 32 bits
>>> from
>>> mingw-builds.
>>> I posted that to gcc bugs:
>>>
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69832
>>>
>>> but as you can see it seems only related to mingw-w64
>>>
>>> What can be done?
>>
>> Hi,
>>
>> Can you try 4.9.3...5.3.0?
>>
>>
>> --
>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>> Monitor end-to-end web transactions and take corrective actions now
>> Troubleshoot faster and improve end-user experience. Signup Now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
>> ___
>> Mingw-w64-public mailing list
>> Mingw-w64-public@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>
> --
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public 


--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] internal compiler error 4.9.2

2016-03-14 Thread Victor Bombi
The same intenal error is happening

- Original Message - 
From: "niXman" <i.nix...@autistici.org>
To: <mingw-w64-public@lists.sourceforge.net>
Sent: Thursday, March 03, 2016 5:45 PM
Subject: Re: [Mingw-w64-public] internal compiler error 4.9.2


>
>> I have got an internal compiler error with mingw-w64 posi-dwarf 32 bits
>> from
>> mingw-builds.
>> I posted that to gcc bugs:
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69832
>>
>> but as you can see it seems only related to mingw-w64
>>
>> What can be done?
>
> Hi,
>
> Can you try 4.9.3...5.3.0?
>
>
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public 


--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] internal compiler error 4.9.2

2016-03-03 Thread niXman

> I have got an internal compiler error with mingw-w64 posi-dwarf 32 bits 
> from
> mingw-builds.
> I posted that to gcc bugs:
> 
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69832
> 
> but as you can see it seems only related to mingw-w64
> 
> What can be done?

Hi,

Can you try 4.9.3...5.3.0?


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


[Mingw-w64-public] internal compiler error 4.9.2

2016-03-03 Thread Victor Bombi
Hello,

I have got an internal compiler error with mingw-w64 posi-dwarf 32 bits from
mingw-builds.
I posted that to gcc bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69832

but as you can see it seems only related to mingw-w64

What can be done?

Bet regards

victor bombi


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


[Mingw-w64-public] internal compiler error: Segmentation fault, MinGW-W64 4.8.1

2015-08-10 Thread Peter Foelsche
source code:

https://onedrive.live.com/redir?resid=2BFA22F3AB9E833!59288authkey=!AAxbkAffcBIxUTAithint=file%2cbz

Compiled with:

g++ -shared -DNDEBUG -w -xc++ -shared -o 1.dll -O3 -funroll-loops 
-march=native -mno-avx -ffast-math -Xlinker --enable-auto-import 
hisimsoi_fb_va.cpp

on windows 7 64.
Produces the following error message:

hisimsoi_fb_va.cpp: In function 'const CNoiseCalculator* 
noise(CInstanceData*, const double*, const double*, const double*, 
void*, double*, double*)':
hisimsoi_fb_va.cpp:139588:32: internal compiler error: Segmentation fault
  static const CNoiseCalculator *noise(
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See http://sourceforge.net/projects/mingw-w64 for instructions.


Compiles fine on LINUX with g++ 4.5.2 and g++ 4.9.2

-- 
This email may contain material that is confidential and/or proprietary 
that the sender intended only for specific recipients. Any review by 
unintended recipients, forwarding or creating derivative works without the 
written permission of Silvaco, Inc http://silvaco.com. or its 
subsidiaries is strictly prohibited. If you are not the intended recipient, 
please contact the sender and delete all copies.

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] internal compiler error: Segmentation fault, MinGW-W64 4.8.1

2015-08-10 Thread Peter Foelsche
on windows:

g++ (GCC) 4.8.2 -- crashes

g++ (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 5.1.0 -- works fine


-- 
This email may contain material that is confidential and/or proprietary 
that the sender intended only for specific recipients. Any review by 
unintended recipients, forwarding or creating derivative works without the 
written permission of Silvaco, Inc http://silvaco.com. or its 
subsidiaries is strictly prohibited. If you are not the intended recipient, 
please contact the sender and delete all copies.

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


[Mingw-w64-public] Internal compiler error: Error reporting routines re-entered.

2014-02-19 Thread Wim Bekker
Suddenly this morning I receive the error message below. What can I do
about it?

Internal compiler error: Error reporting routines re-entered.

Please submit a full bug report,

with preprocessed source if appropriate.

See mingw-w64-public@lists.sourceforge.net for instructions.
Makefile.Debug:1529: recipe for target `debug/rmc_test.o' failed

mingw32-make[1]: *** [debug/rmc_test.o] Error 1
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] Internal compiler error: Error reporting routines re-entered.

2014-02-19 Thread JonY
On 2/17/2014 18:17, Wim Bekker wrote:
 Suddenly this morning I receive the error message below. What can I do
 about it?
 
 Internal compiler error: Error reporting routines re-entered.
 
 Please submit a full bug report,
 
 with preprocessed source if appropriate.
 
^^^

It's a gcc bug, we can't help unless you give us details on what you
were doing.

What version of gcc are you using? How did you obtain it? Where did you
get it from? What OS are you running it on?

Post the command line you were using to compile the failing file, along
with the preprocessed code. Since it is C++, you may want to use 7z or
tar.xz to compress it.

You may also want to talk to the gcc-help mailing list.




signature.asc
Description: OpenPGP digital signature
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


[Mingw-w64-public] Internal compiler error: Error reporting routines re-entered.

2014-02-18 Thread Wim Bekker
Suddenly this morning I receive this error message:

Internal compiler error: Error reporting routines re-entered.

Please submit a full bug report,

with preprocessed source if appropriate.

See mingw-w64-public@lists.sourceforge.net for instructions.



I figured it out that it happens when I call vector::emplace_back for an
object with not enough parameters. If I supply enough parameters no
compilation error and thus no internal compiler error.


I use g++ (rubenvb-4.7.4-release) 4.7.3.
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public