On Wed, 2009-10-14 at 08:33 +0200, Michael Matz wrote:
> So, why not just move them to dead-branches now, and be done with it?
OK, your argument has convinced me. :-)
Cheers,
Ben
On Wed, 2009-10-14 at 23:56 +0530, sandeep soni wrote:
> On Wed, Oct 14, 2009 at 9:02 PM, Tobias Grosser
> wrote:
> > On Wed, 2009-10-14 at 20:12 +0530, sandeep soni wrote:
> >> > Hi,
> >> >
> >> > you also might want to take a look at the Graphite project.
> >> > http://gcc.gnu.org/wiki/Graphite
Hi,
> Ok, I've actually gone a different route. Instead of waiting for the
> middle end to perform this, I've directly modified the parser stage to
> unroll the loop directly there.
I think this is a very bad idea. First of all, getting the information
needed to decide at this stage whether unro
2009/10/14 Ben Bridgwater:
> Can anyone tell me why this template constructor only works at global scope?
http://gcc.gnu.org/bugs/ or the gcc-help mailing list.
This mailing list is for discussing development of GCC, not help using it.
> I realize I could use a std::initializer_list constructor
Hello All
Is the following scenario possible:
gcc-4.5 is being released at Christmas 2009 [*]. Since it is a
production compiler, it has been compiled without any checking (no
ENABLE_CHECKING, etc...)
a plugin foo.c is compiled as foo.so for that gcc-4.5, but since the
plugin is probably bu
Can anyone tell me why this template constructor only works at global scope?
Is this a g++ bug (I'm using g++ 4.5)?
// g++ -std=c++0x t.cpp
class T {
public:
template
T(int (&a)[N]) {}
};
T t1 = (int[]) {1, 2, 3}; // OK
int main(int argc, char **argv)
{
T t2 = (int[]) {1, 2, 3}; // error
We should also keep in mind that such logs aimed at users should support
i18n - unlike the existing dumps for compiler developers, which are quite
properly English only, and most calls to internal_error which should only
appear if there is a compiler bug and are also only meant to be useful for
-Winline doesn't help here. Scanning the assember output does (obviously!).
nm also does.
Paolo
Ok, I've actually gone a different route. Instead of waiting for the
middle end to perform this, I've directly modified the parser stage to
unroll the loop directly there.
Basically, I take the parser of the for and modify how it adds the
various statements. Telling it to, instead of doing in the
On Wed, Oct 14, 2009 at 9:02 PM, Tobias Grosser
wrote:
> On Wed, 2009-10-14 at 20:12 +0530, sandeep soni wrote:
>> > Hi,
>> >
>> > you also might want to take a look at the Graphite project.
>> > http://gcc.gnu.org/wiki/Graphite where we do loop optimizations and
>> > automatic parallelization bas
Hi Joern and list(s),
On Wed, Oct 14, 2009 at 12:05 PM, Joern Rennecke
wrote:
> He also said that it was a different machine, Core 2 Q6600 vs
> some kind of Xeon Core 2 system with a total of eight cores.
> As different memory subsystems are likely to affect the code, it
> is not an established r
Jan Hubicka wrote:
Yes, I would be interested. It seems that for osme reason the other
functions are not considered to be called once, perhaps a visibility
issue. We also should say what limit was reached on inlining hlprog.
Sent off bzip2'd tar file.
--
Toon Moene - e-mail: t...@moene.org
On Wed, Oct 14, 2009 at 04:33:35PM +0200, Jan Hubicka wrote:
> > Deciding on smaller functions:
> > Considering inline candidate phcall_.clone.3.
> > Inlining failed: --param max-inline-insns-auto limit reached
> Yes, I would be interested. It seems that for osme reason the other
> functions are
On Wed, 2009-10-14 at 20:12 +0530, sandeep soni wrote:
> > Hi,
> >
> > you also might want to take a look at the Graphite project.
> > http://gcc.gnu.org/wiki/Graphite where we do loop optimizations and
> > automatic parallelization based on the polytop model. If you need any
> > help feel free to
> Hi,
>
> you also might want to take a look at the Graphite project.
> http://gcc.gnu.org/wiki/Graphite where we do loop optimizations and
> automatic parallelization based on the polytop model. If you need any
> help feel free to ask.
>
> Tobias
>
>
Hi,
This seems to be quite interesting and ch
> Richard Guenther wrote:
>
> >It'll be in /tmp and named after the first object file, in your case it
> >will
> >be ccGGS24.o.047i.inline (because the first object file will be a
> >tempfile). A minor inconvenience that maybe is going to be fixed.
>
> Now that Richard has pointed out to me whe
> Huh. I've never seen this before. Is this with your patches to
> generate a "single executable" or without?
My patches are applied, but shouldn't be activated, because
I haven't defined SINGLE_EXECUTABLE.
I could try taking it back to raw 3.4.6 though and see if that has
the same problem.
Joern Rennecke wrote:
Quoting Mark Tall :
Joern Rennecke wrote:
But at any rate, the subject does not agree with
the content of the original post. When we talk
about a 'regression' in a particular gcc version,
we generally mean that this version is in some
way worse than a previous version of
Richard Guenther wrote:
It'll be in /tmp and named after the first object file, in your case it will
be ccGGS24.o.047i.inline (because the first object file will be a
tempfile). A minor inconvenience that maybe is going to be fixed.
Now that Richard has pointed out to me where the info is, I
Richard Guenther wrote:
On Tue, Oct 13, 2009 at 8:31 PM, Toon Moene wrote:
gfortran -o exe -O3 -flto -fwhole-program -fdump-ipa-inline a.f lib.a
?
It'll be in /tmp and named after the first object file, in your case it will
be ccGGS24.o.047i.inline (because the first object file will be a
學習記憶法真的很便宜1600元不出門也可以學習 快來試試看喔。請按下面plurk(噗浪)的連結，就可以知道詳情了
---
到底下的鏈結來瞧瞧 讓大腦快速動起來的方法只要1600元 的 Plurk 頁面：
http://www.plurk.com/pbms1/invite/2
Plurk.com 是一個讓保持聯繫變得十分容易且有趣的社交日誌。
_
Opt Out of Plurk emails:
This email was sent in connection with you Plurk.com membership
Quoting Mark Tall :
Joern Rennecke wrote:
But at any rate, the subject does not agree with
the content of the original post. When we talk
about a 'regression' in a particular gcc version,
we generally mean that this version is in some
way worse than a previous version of gcc.
Didn't the orig
On Tue, Oct 13, 2009 at 8:31 PM, Toon Moene wrote:
> Jeff Law wrote:
>
>> On 10/10/09 09:17, Daniel Jacobowitz wrote:
>
>>> On Sat, Oct 10, 2009 at 02:31:25PM +0200, Jan Hubicka wrote:
>>>
My solution would be probably to pass -fdump-ipa-inline parameter to lto
compilation and read
23 matches
Mail list logo
