On 09/14/09 11:52:11, Richard Guenther wrote:
> > What approach would you recommend for the
> > implementation of UPC tree re-writes that will
> > support calls to the runtime (that are inlined,
> > if applicable)?
>
> Without reading all the details of your mail I suggest that you
> perform a cus
(I'm copying this thread back to the main GCC list, to
document the problem that we ran into, RG's suggestion
and the fix that we made.)
While merging our GCC/UPC implementation with
the GCC trunk, we ran into a situation where
some tests failed on the check shown below in
verify_gimple_assign_sin
Hi all,
I have the following function:
unsigned int fact_aux(unsigned int n, unsigned int k)
{
if(n == 0)
return k;
else
return fact_aux(n - 1, k * n);
}
unsigned int facti(unsigned int n)
{
return fact_aux(n, 1);
}
Gcc4.3.4 when I compile functions with : -Os -fno-i
on GCC-trunk/Cygwin/Core2 I observe the following behaviour.
g++ -std=gnu++0x -O2 -m32 -march=native -msse -msse2 -msse3 -Wall
-Werror -Wno-unused -Wno-strict-aliasing -march=native
-fomit-frame-pointer -Wno-pmf-conversions -g main.cpp
---8<--
#include
int test1(__m128i v)
Gary Funck writes:
> Do you/others on this list have a reference that supports
> the statement: "Treating uninitialized variables
> as common variables is a non-standard extension even for C90."?
> (I did see a thread on this list, late April 1999, that
> discussed some of the issues, but nothing
I would like to know if the exception handling software has changed
between 4.1 and 4.3.
I have developed a module to generate gcc compatible dwarf debug info
and it works with gcc 4.1. It is in the context of a JIT.
Now I have some mysterious crashes with gcc 4.3 under Suse 11.
Ubuntu seems to
Hi,
I am trying to walk through the body of the current_function_decl in
TARGET_FUNCTION_OK_FOR_SIBCALL for a specific arch in gcc 4.3.4. I am
using DECL_SAVED_TREE but it's not working as I expect.
For the c file:
extern unsigned int source_size(void *s);
extern void source_drop_no_checks(void *s
On Thu, Jan 14, 2010 at 3:12 AM, Paulo J. Matos wrote:
> Gcc4.3.4 when I compile functions with : -Os -fno-inline-functions
> -fno-inline-small-functions
> calls TARGET_FUNCTION_OK_FOR_SIBCALL for the fact_aux call in facti,
> but it does not call TARGET_FUNCTION_OK_FOR_SIBCALL for the fact_aux
>
On 01/14/10 08:26:31, Ian Lance Taylor wrote:
> Online I found this:
>
> http://www.faqs.org/docs/artu/c_evolution.html
>
> [T]he ANSI Draft Standard finally settled on definition-reference
> rules in 1988. Common-block public storage is still admitted as
> an acceptable variatio
Hi,
i'd like to submit a bug report. I read the instructions on
http://gcc.gnu.org/bugs, but i do not really know where the crash
happens and what causes the crash to happen. I therefore just wrote
the instructions below - they're simple. If you still need more
specific stuff, please send me a pri
fanqifei wrote:
2010/1/13 Bingfeng Mei :
Your instruction is likely too specific to be picked up by GCC.
You may use an intrinisc for it.
Bingfeng
but insv is a standard pattern name.
the semantics of expression x= (x&0xFF00) | ((i<<16)&0x00FF);
is exactly what insv can do.
I all trie
2010/1/14 Christoph Rupp:
>
> To reproduce, these steps are necessary:
>
> wget http://crupp.de/dl/hamsterdb-1.1.1.tar.gz
> tar -zxvf hamsterdb-1.1.1.tar.gz
> cd hamsterdb-1.1.1
> ./configure --enable-internal
> make
There are lots of these warnings, which you ignore at your peril:
freelist.c:332
On Thu, 14 Jan 2010 22:44:11 +0100
Christoph Rupp wrote:
> To reproduce, these steps are necessary:
>
> wget http://crupp.de/dl/hamsterdb-1.1.1.tar.gz
> tar -zxvf hamsterdb-1.1.1.tar.gz
> cd hamsterdb-1.1.1
> ./configure --enable-internal
> make
> make test # this will segfault after a few tests
Snapshot gcc-4.5-20100114 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.5-20100114/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
David Daney writes:
>> but insv is a standard pattern name.
>> the semantics of expression x= (x&0xFF00) | ((i<<16)&0x00FF);
>> is exactly what insv can do.
>> I all tried mips gcc cross compiler, and ins is also not generated.
>
> You must be doing something wrong:
>
> $ cat fanqifei.c
>
fanqifei writes:
> 2010/1/13 fanqifei :
>> Hi,
>> I am working on a micro controller and trying to port gcc(4.3.2) for it.
>> Not the compiling process runs into the following error:
>> a.c: In function 'task':
>> a.c:150: error: unrecognizable insn:
>> (insn 479 478 320 19 a:381 (set (reg:SI 12
Piotr Wyderski writes:
> Are these known issues?
If you don't find them in http://gcc.gnu.org/bugzilla/ , please file
them there as described in http://gcc.gnu.org/bugs/ .
Thanks.
Ian
jacob navia writes:
> I would like to know if the exception handling software has changed
> between 4.1 and 4.3.
>
> I have developed a module to generate gcc compatible dwarf debug info
> and it works with gcc 4.1. It is in the context of a JIT.
>
> Now I have some mysterious crashes with gcc 4.
hi...
i was seeing an infinite recursion in gen_lsm_tmp_name() in trunk.
it only happened with my code, when my __attribute__((restrict)) patch
is applied.
i dont really know how to reproduce it without it.
but the relevant place doesnt look like its supposed to be a
fallthrough.
see attached
19 matches
Mail list logo
