On 22.02.2010 22:41, Janis Johnson wrote:
On Mon, 2010-02-22 at 13:11 -0800, Andrew Pinski wrote:
On Mon, Feb 22, 2010 at 1:06 PM, Janis Johnson wrote:
If you can reproduce the problem with a small, self-contained test then
please file a bug report. It might be possible to issue a warning or
On Mon, 2010-02-22 at 13:11 -0800, Andrew Pinski wrote:
> On Mon, Feb 22, 2010 at 1:06 PM, Janis Johnson wrote:
> > If you can reproduce the problem with a small, self-contained test then
> > please file a bug report. It might be possible to issue a warning or
> > to detect that the loop should n
On Mon, Feb 22, 2010 at 1:06 PM, Janis Johnson wrote:
> If you can reproduce the problem with a small, self-contained test then
> please file a bug report. It might be possible to issue a warning or
> to detect that the loop should not be vectorized. If not, maybe the
> compiler should disable v
On Mon, 2010-02-22 at 21:17 +0100, Christoph Rupp wrote:
> 2010/2/20 Richard Guenther :
> > On Sat, Feb 20, 2010 at 1:38 PM, Christoph Rupp wrote:
> [...]
> >> I fixed all warnings regarding dereferencing type-punned pointers and
> >> I compile with -O3 AND -fno-strict-aliasing.
> >>
> >> and i st
2010/2/20 Richard Guenther :
> On Sat, Feb 20, 2010 at 1:38 PM, Christoph Rupp wrote:
[...]
>> I fixed all warnings regarding dereferencing type-punned pointers and
>> I compile with -O3 AND -fno-strict-aliasing.
>>
>> and i still get the same crash as earlier. it does not crash with -O2.
>>
>> Fr
On Sat, Feb 20, 2010 at 1:38 PM, Christoph Rupp wrote:
> Hi Jonathan & list,
>
> this is a follow-up on an email from mid-january - i had crashes when
> compiling my library with -O3. I fixed all warnings "dereferencing
> type-punned pointer will break
>> strict-aliasing rules" and got it running.
Hi Jonathan & list,
this is a follow-up on an email from mid-january - i had crashes when
compiling my library with -O3. I fixed all warnings "dereferencing
type-punned pointer will break
> strict-aliasing rules" and got it running.
(at least i thought so - now i experience crashes again so maybe
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
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
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
10 matches
Mail list logo