sandeep soni writes:
> I have been studying the gcc code lately as part of my project.I have
> got info from this mailing list about CFG and DFG information.I want
> to know how gcc uses this information to perform loop optimization?
> Does it Follow any particular algorithm or in particular what
Snapshot gcc-4.3-20091011 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.3-20091011/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.3 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
On Fri, 2009-09-25 at 16:55 +, Joseph S. Myers wrote:
> Do we believe any future conversion to another version control system
> (that might have a more structured notion of what is a branch than it
> simply being a directory used in a certain way) would continue to make the
> history of suc
Jakub Jelinek wrote:
> The above mentioned patch adds support for raw strings and u8.
>
Indeed. I have just committed the below too.
Paolo.
//
2009-10-11 Paolo Carlini
* htdocs/projects/cxx0x_status.html: Unicode string literals are
unsupported in 4.4.
Index: ht
On Sun, Oct 11, 2009 at 10:42:41AM -0700, Andrew Pinski wrote:
> On Sun, Oct 11, 2009 at 10:36 AM, Paolo Carlini
> wrote:
> > Hi again,
> >> To my best knowledge the feature is not implemented at all, thus a bug
> >> in the C++0x Support page.
> > Following up to my previous message, I figured out
On Sun, Oct 11, 2009 at 10:36 AM, Paolo Carlini
wrote:
> Hi again,
>> To my best knowledge the feature is not implemented at all, thus a bug
>> in the C++0x Support page.
> Following up to my previous message, I figured out a probable reason for
> the mistake: actually we *do* have a patch impleme
On Sun, Oct 11, 2009 at 7:31 AM, Paolo Carlini wrote:
> Hi Beman
>> http://gcc.gnu.org/projects/cxx0x.html shows Unicode string literals (N2442)
>> as
>> being supported in gcc 4.4. But this little program fails to compile:
>>
>> #include
>> int main()
>> {
>> std::cout << u8"foo" << std::endl
Hi again,
> To my best knowledge the feature is not implemented at all, thus a bug
> in the C++0x Support page.
Following up to my previous message, I figured out a probable reason for
the mistake: actually we *do* have a patch implementing the feature,
which however has not been applied yet to mai
On Sun, Oct 11, 2009 at 6:21 PM, Richard Guenther
wrote:
> On Sun, Oct 11, 2009 at 6:04 PM, Rainer Emrich
> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> libtool: link: gcc -shared .libs/lto-plugin.o
>> -
>> -L/SCRATCH/tmp.dYgZv17836/Linux/x86_64-unknown-linux-gnu/openSUSE_10.
On Sun, Oct 11, 2009 at 6:04 PM, Rainer Emrich
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> libtool: link: gcc -shared .libs/lto-plugin.o
> -
> -L/SCRATCH/tmp.dYgZv17836/Linux/x86_64-unknown-linux-gnu/openSUSE_10.3/install/lib64
is there a libiberty in that path?
> - -lelf
> -
>
(Version 4.5.0)
There are plugin callbacks which trigger at the end of processing types
and C++ functions,
but I can not find a clean way for plugin code to notice a top-level
variable declaration.
I'm hoping that the answer does not require the plugin shared library to
bind to global symbols
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
libtool: link: gcc -shared .libs/lto-plugin.o
-
-L/SCRATCH/tmp.dYgZv17836/Linux/x86_64-unknown-linux-gnu/openSUSE_10.3/install/lib64
- -lelf
-
-L/SCRATCH/tmp.dYgZv17836/Linux/x86_64-unknown-linux-gnu/openSUSE_10.3/gcc-4.5.0/gcc-4.5.0/libiberty/pic
- -
Hi Joern,
On Sat, Oct 10, 2009 at 5:27 PM, Joern Rennecke
wrote:
> Quoting Li Feng :
>>
>> So my question is,
>>
>> 1. Is this necessary/correct if we want to escape the re-optimization for
>> the
>> first few passes before tree-parloop.c and continue the optimization
>> passes
>> after it for th
Hi All,
I have been studying the gcc code lately as part of my project.I have
got info from this mailing list about CFG and DFG information.I want
to know how gcc uses this information to perform loop optimization?
Does it Follow any particular algorithm or in particular what are the
different tec
Hi Beman
> http://gcc.gnu.org/projects/cxx0x.html shows Unicode string literals (N2442)
> as
> being supported in gcc 4.4. But this little program fails to compile:
>
> #include
> int main()
> {
> std::cout << u8"foo" << std::endl;
> }
>
...
> Is this a bug in gcc? A bug in the C++0x Support
http://gcc.gnu.org/projects/cxx0x.html shows Unicode string literals (N2442) as
being supported in gcc 4.4. But this little program fails to compile:
#include
int main()
{
std::cout << u8"foo" << std::endl;
}
C:\gcc>bin\g++ -std=gnu++0x u8-literal.cpp
u8-literal.cpp: In function 'int main()':
16 matches
Mail list logo