suggest why making a "bootstrap" "C" "--enable-languages=c"
compiler should then
go on to build "C++" ?
I'm pretty sure the above error would not have occurred without the
kernel lock-up and interruption,
but nevertheless, I didn't ask the gcc build system to build C++ yet,
so why did it do so ?
Any ideas / comments would be much appreciated ,
Jason Vas Dias (a Software Engineer)
compiler and libstdc++ ?
Thanks & Regards,
Jason
On Sun, Jul 8, 2012 at 4:06 PM, Jason Vas Dias wrote:
> Hi - I've been regularly building gcc for nearly two decades, and now
> attempting to build a bootstrap
> "C" only gcc-4.7.1 sufficient only to build binutils (my in
I really do not think a '-Wpedantic -Wconversion' warning should
be generated for the following code, but it is
(with GCC 6.4.1 and 7.3.1 on RHEL-7.5 Linux) :
$ echo '
typedef unsigned short U16_t;
static void f(void)
{ U16_t a = 1;
a-=1;
}' > t.C;
$ g++ -std=c++14 -Wall -Wextra -pedant
Great thanks for your informative response, Jim! :
RE:
On 23/04/2018, Jim Wilson wrote:
> On 04/23/2018 07:11 AM, Jason Vas Dias wrote:
>>
>> I really do not think a '-Wpedantic -Wconversion' warning should
>> be generated for the following code, but it is
>>
