Status
==
GCC 4.8.1 has been released, the branch is again open
for regression bugfixes and documentation fixes.
GCC 4.8.2 could be tentatively released in early September.
Curious user is curious about 4.8.2 status! :^)
Using binutils 2.15.96 and gcc 3.4.3... where have I gone wrong?
-Jason
gcc -c -g -DENABLE_CHECKING -DENABLE_ASSERT_CHECKING -DIN_GCC -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -Wno-error -DHAVE_CONFIG_H -DGENERATOR_FILE-I.
-Ibuild
A little humor from a long time ML lurker...
Via C3-2 Nehemiah 1GHz 512MB ddr
$ ../gcc-4.0.0/configure --prefix=/home/jason/local/gcc-400 --enable-shared
\
--enable-threads=posix --disable-checking --enable-long-long
--enable-__cxa_atexit \ --enable-clocale=gnu --disable-libunwind-exceptions
I suspect this line is the source of your problems:
friend Tclass Y* funcY, X(TX* p);
Y isn't a template parameter here, but a (concrete?) class named Y.
The below compiles with 3.4.3 anyways...
Regards,
-Jason
// Line 1
class A {
public:
A() { };
~A() { };
};
class B {
public:
B();
Vincent Lefevre writes:
while ((*(q++))-- == 0) ;
Is that defined and legal?? Is q incremented before or after *q is
decremented? They are both post operators!
Jason Mancini
_
Rediscover Hotmail®: Get e-mail storage
Web search shows that -Wmaybe-uninitialized is an imprecise check, and that
boost::optional is already a known sore spot, but I wanted to pass along this
small test case in case the warning's owner wanted to do further improvements.
We solved our one grumpy instance with auto x =
Been doing stability testing on my x86_64 Ryzen cpu using openSUSE's
(Tumbleweed) "gcc7.1.1 20170802" + compiling Linux kernel source. Every so
often, the build curiously stalls on a futex between cc1 and as. cc1 is on the
futex. as is waiting to read. Could that hang be related to what's
Any notable ABI changes from 9 to 10?
Thanks!
-Jason
(Sorry for asking here, there was no response from gcc-help in January.)
