gcc-python-plugin is a plugin for GCC 4.6 onwards which embeds the
CPython interpreter within GCC, allowing you to write new compiler
warnings in Python, generate code visualizations, etc.
It ships with "gcc-with-cpychecker", which implements static analysis
passes for GCC aimed at finding bugs in
> Assuming that the new implementation will be available in time for 4.9, my
> primary concern is that in the meanwhile running the libstdc++ testsuite will
> be quite noticeably slower. Do you have some numbers?
Just use the numbers I used the last two times I tried to explain why PCH was
On 11/29/2012 06:30 PM, awarecons wrote:
FreeBSD 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC
2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
i386
chromium-23.0.1271.64_1 compiled perfectly.
But chromium-23.0.1271.91 fails:
Looks like you aren't building with cu
FreeBSD 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC
2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
i386
chromium-23.0.1271.64_1 compiled perfectly.
But chromium-23.0.1271.91 fails:
...
In file included from ./base/global_descriptors_posix.h:15:0,
Hello,
I have been looking at a piece of code that fails to vectorize because GCC4.7.0
is unable in suportable_widening_operation to provide proper conversions for a
WIDEN_MULT_EXPR. vectype_in is V8HI and vectype_out is V2DI. The problem seems
to be that GCC code at the end of this functions b
Hi,
I notice that if you add a DRIVER_SELF_SPEC option and then add that
option as a MULTILIB_OPTION, it doesn't build certain libraries for
that multilib variant.
for example, if you add:
"%{mtestoption:-mcpu=cortex-a5 %
