Jan Hubicka <[EMAIL PROTECTED]> writes:
> in testsuite there are few reduced testcases where unit growth (an
> inliner limit - inliner is allowed to inline as long as the unit don't
> grow by given percentage, set to 50%) is too strict.
Out of curiousity, have you considered permitting inlining l
Romain Failliot wrote:
Yes, but you have to be careful, with a license statement like
the above, you probably have to adopt a chinese wall strategy,
i.e. anyone who has seen the run time library that is so
licensed should not be allowed to work on the implementation of
the replacement.
David s
> Yes, but you have to be careful, with a license statement like
> the above, you probably have to adopt a chinese wall strategy,
> i.e. anyone who has seen the run time library that is so
> licensed should not be allowed to work on the implementation of
> the replacement.
David send me a more exp
Romain Failliot wrote:
2005/11/13, Florian Weimer <[EMAIL PROTECTED]>:
There is a GCC front end, but it has zero chance of being integrated
into FSF GCC at this stage. The run-time library license contains
this little gem:
* (ii) Any derived versions of this software (howsoever m
22561: (wrong-code) ca11c01
18819: (wrong-code) cdd2a02
I am pretty sure these are the same problem. They are also the only
ones failing in my tree for x86_64.
2005/11/13, Florian Weimer <[EMAIL PROTECTED]>:
> There is a GCC front end, but it has zero chance of being integrated
> into FSF GCC at this stage. The run-time library license contains
> this little gem:
>
> * (ii) Any derived versions of this software (howsoever
> modified)
> *
On Nov 12, 2005, at 11:43 PM, Steven Woody wrote:
how can i get see the runtime memory useage graph for my c++
program? this will
include stack memory and dynamic memory (heap). thanks.
This is an OS question, and gcc isn't an OS, so this is the wrong
place to ask. I usually use top, leaks
On Sun, 2005-11-13 at 22:20 +0100, Steven Bosscher wrote:
> On Sunday 13 November 2005 22:02, Jeffrey A Law wrote:
> > No great insights on how to make dbr_schedule CFG aware -- just
> > remember that a filled delay slot can represent 3 different cases:
> >
> > 1. An extension of the block contai
On Sunday 13 November 2005 22:02, Jeffrey A Law wrote:
> No great insights on how to make dbr_schedule CFG aware -- just
> remember that a filled delay slot can represent 3 different cases:
>
> 1. An extension of the block containing the sequence.
>
> 2. An extension of the block at the target
On Sun, 2005-11-13 at 21:20 +0100, Steven Bosscher wrote:
> Hi,
>
> I'm trying to figure out how much effort it would take to make
> dbr_schedule CFG aware. One of the issues I'm running into is
> that the RTL CFG stuff doesn't support SEQUENCEs at all. So if
> I have a delay slot filled, e.g.,
I have tried to compile
...
double ***v;
v = new double **[100];
...
in different classes. Sometimes the program shows a sigsegv at the new
operator. Using gdb the code has called the following functions:
operator new[]() -> operator new() -> malloc () -> _int_malloc()
Is this a g++-3
Hi,
I'm trying to figure out how much effort it would take to make
dbr_schedule CFG aware. One of the issues I'm running into is
that the RTL CFG stuff doesn't support SEQUENCEs at all. So if
I have a delay slot filled, e.g.,
(sequence [
(jump_insn (...)) ;; The branch with delay slots
> Is it plan to add the D language in the ones that
are supported by
GCC
> by default?
I have been following the D language for some time.
In many ways it mirrors my own ideas on language
design. In my oppinion the biggest thing holding it
back is the lack of good tools.
If some folks are inte
On Sun, Nov 13, 2005 at 07:19:49PM +, Graham Stott wrote:
>
> It's done during configury
Ah:
mips*-*-*)
gcc_GAS_CHECK_FEATURE([explicit relocation support],
gcc_cv_as_mips_explicit_relocs, [2,14,0],,
[ lw $4,%gp_rel(foo)($4)],,
[if test x$target_cpu_default = x
It's done during configury
Cheers
Graham
On Sun, Nov 13, 2005 at 07:20:42PM +0100, Steven Bosscher wrote:
> Hi,
>
> This is a bit of a silly question, maybe, and I feel kinda stupid that
> I have to ask, but grep doesn't help and looking through ChangeLogs is
> not getting me any further either.
>
> So...
>
> Where does the MIPS backen
This is the beta release of binutils 2.16.91.0.4 for Linux, which is
based on binutils 2005 0821 in CVS on sources.redhat.com plus various
changes. It is purely for Linux.
The new i386/x86_64 assemblers no longer accept instructions for moving
between a segment register and a 32bit memory location
Hi,
This is a bit of a silly question, maybe, and I feel kinda stupid that
I have to ask, but grep doesn't help and looking through ChangeLogs is
not getting me any further either.
So...
Where does the MIPS backend define TARGET_EXPLICIT_RELOCS? It is used
in a lot of places in this backend, bu
After Eric commit for 24003, ACATS FAIL are down to eight
on x86 and x86_64-linux:
http://gcc.gnu.org/ml/gcc-testresults/2005-11/msg00616.html
http://gcc.gnu.org/ml/gcc-testresults/2005-11/msg00615.html
Five PRs are covering those failures:
common x86 & x86_64
22333: (wrong-code) c34007p c34007r
On Sunday 13 November 2005 08:23, Richard Kenner wrote:
> > A "function-never-returns-null" attribute doesn't seem like
> > the right mechanism. Instead, there should be a "never-null"
> > attribute on pointer types. A "function-never-returns-null" is
> > just a function whose ret
> A patch to fix this regression was committed earlier today to GCC4.1.
Works fine on SPARC. Thanks!
--
Eric Botcazou
Hi Eric,
A patch to fix this regression was committed earlier today to GCC4.1.
Razya
> Hi Razya,
>
> > Yes, I am aware of this problem.
> > It does not fail for power and I'm trying to figure out why it fails
for
> > x86 architecture.
> > It appears that the type of the constant being passed
Hi Razya,
> Yes, I am aware of this problem.
> It does not fail for power and I'm trying to figure out why it fails for
> x86 architecture.
> It appears that the type of the constant being passed to a function having
> a short parameter, is an int while I expected it to be short.
>
> call to g :
* Steven Woody:
> i want to check in my C++ program, what variable is allocated in where. is
> there such a tool?
> how can i get see the runtime memory useage graph for my c++
> program? this will include stack memory and dynamic memory
> (heap). thanks.
To some extent, valgrind can generate su
Richard Guenther wrote:
And this is why there seemed to be consensus to merge the two in the
middle-end and preserve debug-info somehow differently. Like with
a "frontend type-id" on the decl. That would allow lowering of f.i.
integral types to their modes at some point, too.
It seems a clea
i want to check in my C++ program, what variable is allocated in where. is
there such a tool?
another relative question is, where the 'new' operator get memory from? the
global heap? does it same with what 'malloc' get from?
thanks.
--
steven woody (id: narke)
Celine: Well, who says relation
On 13 Nov 2005 02:00:08 +0100, Gabriel Dos Reis
<[EMAIL PROTECTED]> wrote:
> Andrew Pinski <[EMAIL PROTECTED]> writes:
>
> | >
> | > Andrew Pinski <[EMAIL PROTECTED]> writes:
> | >
> | > | > | of what the semantics of REFERENCE_TYPE are/should be, then yes.
> | > | >
> | > | > See, it is not a sema
27 matches
Mail list logo
