On Tue, 7 Jul 2009, Diego Novillo wrote:
> 4- Test on primary and secondary platforms. What is the current
>suggested list of platforms?
http://gcc.gnu.org/gcc-4.5/criteria.html
On Wed, Jul 8, 2009 at 03:15, Kaveh R. GHAZI wrote:
> On Tue, 7 Jul 2009, Diego Novillo wrote:
>
>> 4- Test on primary and secondary platforms. What is the current
>> suggested list of platforms?
>
> http://gcc.gnu.org/gcc-4.5/criteria.html
Thanks. I've filtered the non-ELF platforms from bot
Hi!
Richard asked also for numbers from Linux kernel build, so I've built
linux-2.6 git faf80d62e44dc627efb741f48db50c1858d1667c
make allyesconfig; make on x86_64.
With make allyesconfig; make -j64 and tr...@148582
(--enable-checking=release) it took 9m12s, with v...@149180 it took 9m15s.
With ma
Jakub Jelinek writes:
> [...] With make allyesconfig; [...]
> .debug_info+.debug_loc+.debug_abbrev section sum grew by 1.9MB out
> of 422MB,
I assume this was with var-tracking turned on (due to the toplev.c
AUTODETECT_VALUE logic).
> [...] there locations weren't really changing.
You mean t
On Wed, Jul 08, 2009 at 12:13:46PM -0400, Frank Ch. Eigler wrote:
> Jakub Jelinek writes:
>
> > [...] With make allyesconfig; [...]
> > .debug_info+.debug_loc+.debug_abbrev section sum grew by 1.9MB out
> > of 422MB,
>
> I assume this was with var-tracking turned on (due to the toplev.c
> AUTO
Hello All
I believe gengtype should be enhanced in plugin mode. (I am enhancing it
on the MELT branch first; the rev149385 is still buggy there in plugin
mode...).
First, in plugin mode, gengtype should generate only one output file
(contrarily to what I thought, it should not change anythin
Laurent GUERBY schrieb am Dienstag 12 Mai 2009 um 22:03:
> On Tue, 2009-05-12 at 21:49 +0200, Andreas Schwab wrote:
> > Laurent GUERBY writes:
> > > So 0.15.3 configure does not set $with_ppl variable at all.
> >
> > Sure it does. Look at the argument parsing loop.
>
> I added a dump and $with_pp
I compiled gcc with -g3 -O0' compiler flags to enable invocation of
macros during a gdb session; however, the
macro, PACK_EXPANSION_PATTERN, apparently uses a symbol:
__extension__
not understood by gdb. How can gdb be made to understand
__extension__ or how can __extension__ be rm'ed from
On 07/08/2009 03:11 PM, Larry Evans wrote:
It would be much easier if gdb understood __extension__. Is there a way?
In this case, no. It's protecting a statement expression, which gdb
will never be able to parse.
A better project for helping debug gcc would be to convert all macros
that us
I'm investigating support for decimal floating-point arithmetic in G++.
GCC currently supports this functionality in C for several targets based
on ISO/IEC TR 24732. The C support adds 3 new scalar types: _Decimal32,
_Decimal64, and _Decimal128. With support for mangling those types and
defining
The documentation says:
@deftypefn {Target Hook} bool TARGET_CAN_INLINE_P (tree @var{caller}, tree
@var{callee})
But the code says:
#ifndef TARGET_OPTION_CAN_INLINE_P
#define TARGET_OPTION_CAN_INLINE_P default_target_option_can_inline_p
#endif
#define TARGET_OPTION_HOOKS \
On Wed, Jul 08, 2009 at 03:14:20PM -0700, Richard Henderson wrote:
> On 07/08/2009 03:11 PM, Larry Evans wrote:
> >It would be much easier if gdb understood __extension__. Is there a way?
>
> In this case, no. It's protecting a statement expression, which gdb
> will never be able to parse.
>
> A
Hello,
I recently had the idea that it would be great if GCC/G++ were
integrated into MSVC (I'm sure I'm not the first). That is, if you
could put a user in front of a computer with Visual Studio installed
and for them to be able to write an arbitrary program from start to
finish without realizin
Richard Henderson writes:
> A better project for helping debug gcc would be to convert all macros
> that use statement expressions into proper inline functions. Which
> would then be emitted as out-of-line functions by gcc's -fkeep-inlines
> flag, which would yield something that's callable from
DJ Delorie writes:
> The documentation says:
>
> @deftypefn {Target Hook} bool TARGET_CAN_INLINE_P (tree @var{caller}, tree
> @var{callee})
>
> But the code says:
>
> #ifndef TARGET_OPTION_CAN_INLINE_P
> #define TARGET_OPTION_CAN_INLINE_P default_target_option_can_inline_p
> #endif
>
> #define T
Hello,
my purpose is to write informations about a function by reading its body
from internal representation. I got the body with DECL_SAVED_TREE and I
succeed to get the name of functions and methods called from CALL_EXPR,
using TREE_OPERAND, EXPR_STMT_EXPR, etc... But I can't get the object o
16 matches
Mail list logo