On 11/29/06, Michael Eager <[EMAIL PROTECTED]> wrote:
Ulf Magnusson wrote:
> How are you supposed to find the canonical name of a system (of known
> type) in CPU-Vendor-OS form in the general case? If you have access to
> a system of that particular type, you can run config.guess to find
> out, b
Bobby McNulty wrote:
I received the following error in libstdc++- v3
i686-pc-cygwin and trunk.
/home/Owner/gcc/o/./gcc/xgcc -shared-libgcc
-B/home/Owner/gcc/o/./gcc -n
ostdinc++ -L/home/Owner/gcc/o/i686-pc-cygwin/libstdc++-v3/src
-L/home/Owner/gcc/
o/i686-pc-cygwin/libstdc++-v3/src/.lib
Paolo Bonzini wrote:
for(i = 0;i<*t;i++)
*f += 1.0;
This one is pretty realistic, especially if you consider C++ and inlining:
Don't you think that a convincing argument here has to be based
on actual timings with and without strict aliasing. It would
be interesting to see cases where that
Ulf Magnusson wrote:
While searching for an answer, I noticed that lots of people seem
to have had problems with cross-compilation that to me look more
like problems in the documentation, which I find a bit sad.
Rather than repeatedly complain, the most constructive
contribution would be to co
MPFR 2.2.1 is now available for download from the MPFR web site:
http://www.mpfr.org/mpfr-2.2.1/
Thanks very much to those who tested the release candidates.
The MD5's:
40bf06f8081461d8db7d6f4ad5b9f6bd mpfr-2.2.1.tar.bz2
662bc38c75c9857ebbbc34e3280053cd mpfr-2.2.1.tar.gz
93a2bf9dc66f81caa57c
Hi,
On 2006-11-28 10:39:20 -0800, George R Goffe wrote:
> I'm trying to build the latest svn version of gcc on my hp xw 4300
> system running fedora core 6 and am seeing a problem with mpfr. I
> got the latest mpfr and applied their patch before attempting this
> build. I have a complete build log
On Tue, Nov 28, 2006 at 11:36:19PM -0800, Ian Lance Taylor wrote:
> Or you can use constructor expressions to make this slightly more
> elegant, though I retain the assumptions about type sizes:
>
> char *foo1(char* buf){
> memcpy(buf, (char[]) { 42 }, 1);
> buf += 1;
> memcpy(buf, (short[])
ciao,
guarda questo sito
www.fluupe.com
per i voli low cost è fighissimo
fede
per i voli low cost è il top
www.fluupe.com
se non è chiaro il perche guarda nelle search tips.
ciao
fede
per i voli low cost è il top
www.fluupe.com
se non è chiaro il perche guarda nelle search tips.
ciao
fede
Hi,
In the "GCC Internals manual" it is said that the INSN_CODE(i) is printed in
the debugging output as a small integer followed by a symbolic
representation that locates the pattern in the md file as a small positive
or negative offset from the named pattern. Now, I'm a bit confused. The
followi
> In the "GCC Internals manual" it is said that the INSN_CODE(i) is printed in
> the debugging output as a small integer followed by a symbolic
> representation that locates the pattern in the md file as a small positive
> or negative offset from the named pattern. Now, I'm a bit confused. The
> fo
Basile STARYNKEVITCH <[EMAIL PROTECTED]> writes:
>> I am thinking of extending the *.opt machinery (ie the
>> gcc/opt-functions.awk gcc/optc-gen.awk gcc/opth-gen.awk files) to
>> offer some GCC options which can be disabled or enabled by an
>> appropriate configure flag.
>>
>> More precisely, conf
Hi,
I am considering trying to add DW_AT_start_scope attributes to the
debug info emmited by GCC, so it can be used by GDB. I just wanted to
know what people think about this, and how difficult it is likely to
be?
Thanks for your time.
Rob
> > > I think there are 3 aliasing possibilities here:
> > > 1. known to alias
> > > 2. known to not alias
> > > 3. may alias
> >
> > Actually there is only 2, it may alias or not.
>
> Actually, he's right (and both you and Richard are wrong).
>
> The standard taxonomy of classifications for two
On 11/29/06, Paolo Bonzini <[EMAIL PROTECTED]> wrote:
>> int f(int *a, float *b)
>> {
>> *a = 1;
>> *b = 2.0;
>> return *a == 2;
>> }
>>
>
> Problem: people don't write code that way. (well I hope not)
> People declare a few local variables, load them with data via
> the pointers, do stuff
On 11/29/06, Michael Eager <[EMAIL PROTECTED]> wrote:
Ulf Magnusson wrote:
> While searching for an answer, I noticed that lots of people seem
> to have had problems with cross-compilation that to me look more
> like problems in the documentation, which I find a bit sad.
Rather than repeatedly
> Since humans have to do a bit of alias analysis when maintaining
> or writing code, the extra clarity of pulling things into temporary
> variables isn't wasted.
Sorry, I don't follow. Why should we want to do "a bit of alias analysis"
when maintaining or writing code? It would seem a far bette
"Ulf Magnusson" <[EMAIL PROTECTED]> writes:
> I'd be happy to contribute some documentation on this. I just hope I
> have a firm enough grip on the issue. Where should I send drafts for
> review? Is there some other resource I should be aware of besides
> http://gcc.gnu.org/contribute.html?
Thank
On Wednesday 22 November 2006 16:33, Rafael Espíndola wrote:
> I am working on a ARM backend for LLVM. The problemis that llvm-gcc is
> currently based on gcc 4.0 and I would like to use the new EABI.
>
> I have started to back port the ABI from 4.1 to 4.0. The first attempt
> was to just copy the
Doug Gregor wrote:
> This patch introduces canonical types into GCC, which allow us to
> compare two types very efficiently and results in an overall
> compile-time performance improvement.
Thanks for working on this. It's the sort of project I used to have
time to do. :-)
I will review these p
Ulf Magnusson wrote:
On 11/29/06, Michael Eager <[EMAIL PROTECTED]> wrote:
Ulf Magnusson wrote:
> While searching for an answer, I noticed that lots of people seem
> to have had problems with cross-compilation that to me look more
> like problems in the documentation, which I find a bit sad.
R
I thought Chris was working on updating LLVM to gcc head.
It will be done, but it is not a priority and I need the ARM bits
sooner. Anyway, he will have 5 or 6 patches less to port :-)
Paul
Best Regards,
Rafael
Richard Kenner wrote:
Since humans have to do a bit of alias analysis when maintaining
or writing code, the extra clarity of pulling things into temporary
variables isn't wasted.
Sorry, I don't follow. Why should we want to do "a bit of alias analysis"
when maintaining or writing code? It wou
I guess I can imagine that macro expansion might result in some
cases where strict-aliasing is of benefit. Most people fail to use a
temporary in a macro, probably because __typeof__ is gcc-only.
I can probably fit 20 lines of code on a readable slide. Ideas?
In C++, this:
f (vector &vec)
{
> However, there is still a question which puzzles me a lot? Why gengtype is
> not a sort of filter or generator (like yacc is) taking a (list of) files on
> input and producing a file on output?
It used to take a list of files on its command line, but the list
was so long we were running into len
Hi,
I successfully built gcc 4.1.1 on a Red Hat Enterprise Linux 4
(kernel version 2.6.9-5.EL), and then successfully compiled the Linux
kernel 2.6.18 using that.
Config.guess: i686-pc-linux-gnu
Version (gcc -version):
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: .
I wrote some code (not released yet) that improves the accuracy of
-Wstrict-aliasing using tree-ssa-alias information. The primary idea
was to tell the programmer "go fix the types of variables x and y at
lines ..." when -fstrict-aliasing breaks their code.
It occurred to me that part of th
On Wed, Nov 29, 2006 at 11:02:51AM -0800, Silvius Rus wrote:
>
> I wrote some code (not released yet) that improves the accuracy of
> -Wstrict-aliasing using tree-ssa-alias information. The primary idea
> was to tell the programmer "go fix the types of variables x and y at
> lines ..." when -f
Silvius Rus wrote:
I wrote some code (not released yet) that improves the accuracy of
-Wstrict-aliasing using tree-ssa-alias information. The primary idea
was to tell the programmer "go fix the types of variables x and y at
lines ..." when -fstrict-aliasing breaks their code.
It occurred t
Joel Sherrill wrote:
Silvius Rus wrote:
I wrote some code (not released yet) that improves the accuracy of
-Wstrict-aliasing using tree-ssa-alias information. The primary idea
was to tell the programmer "go fix the types of variables x and y at
lines ..." when -fstrict-aliasing breaks thei
Joe Buck wrote:
If you first prove that there is no cross-type aliasing, then turn on
-fstrict-aliasing, it seems to me that your alias sets won't change at
all. The reason is that if there is a change, it means that you
eliminated an aliasing possibility based on the fact that it's not
allowe
Hi again,
Getting further along with my project, I have come across yet another
thing that I dont understand. While compiling:
libstdc++-v3/libsupc++/vec.cc
My GCC extension comes across two FUNCTION_DECL nodes that both have
DECL_ASSEMBLER_NAME of __cxa_begin_catch
After reading some past
33 matches
Mail list logo
