Jakub Jelinek wrote:
> On Wed, Feb 01, 2012 at 02:00:53PM +0100, Georg-Johann Lay wrote:
>>> * gcc.dg/lto/20091013-1_1.c: xfail for avr.
>>> * gcc.dg/lto/20091013-1_2.c: xfail for avr.
>
> If it is just because of the warnings, can't you
> add
> -Wno-int-to-pointer-cast -Wno-pointer-to-int
On Wed, Feb 01, 2012 at 02:00:53PM +0100, Georg-Johann Lay wrote:
> > * gcc.dg/lto/20091013-1_1.c: xfail for avr.
> > * gcc.dg/lto/20091013-1_2.c: xfail for avr.
If it is just because of the warnings, can't you
add
-Wno-int-to-pointer-cast -Wno-pointer-to-int-cast
to dg-options? Also, not
http://gcc.gnu.org/ml/gcc-patches/2012-01/msg01502.html
Georg-Johann Lay wrote:
> Jakub Jelinek wrote:
>> On Fri, Jan 13, 2012 at 07:40:59PM +0100, Georg-Johann Lay wrote:
>>> The ilp32 is the closes match:
>>>
>>> The source casts pointer to int, int to pointer, long to int, uses 32-bit
>>> init
Jakub Jelinek wrote:
> On Fri, Jan 13, 2012 at 07:40:59PM +0100, Georg-Johann Lay wrote:
>> The ilp32 is the closes match:
>>
>> The source casts pointer to int, int to pointer, long to int, uses 32-bit
>> initializers for int, assumes size_t is unsigned long any maybe others.
>
> No. The source
On 01/13/2012 08:21 PM, Georg-Johann Lay wrote:
> I really don't expect anyone to run test suites on any platform or target
> supported by GCC. Such an approach is completely useless because of the amount
> of time and system resources and I never proposed that.
>
> But it appears that many of th
Rainer Orth schrieb:
Mike Stump writes:
On Jan 13, 2012, at 4:33 AM, Georg-Johann Lay wrote:
This test case is obviously written for 32-bit platforms, thus added
"dg-require-effective-target ilp32" to ensure that the pointer mess won't lead
to FAILs because of
warning: cast to pointer from
On Jan 13, 2012, at 11:25 AM, Georg-Johann Lay wrote:
> So it's fine to dump any code to the test suite no matter on what platform it
> might break or work?
No. It isn't fine, but it does happen. Some people spend a lot of time,
trying to get the testcases minimal, portable and correct. Other
Jakub Jelinek wrote:
> On Fri, Jan 13, 2012 at 08:25:39PM +0100, Georg-Johann Lay wrote:
>> So it's fine to dump any code to the test suite no matter on what platform it
>> might break or work?
>
> It is wrong to knowingly commit testcases that break on such platforms,
> but you really shouldn't e
On Fri, Jan 13, 2012 at 08:25:39PM +0100, Georg-Johann Lay wrote:
> So it's fine to dump any code to the test suite no matter on what platform it
> might break or work?
It is wrong to knowingly commit testcases that break on such platforms,
but you really shouldn't expect every committer to test a
Jakub Jelinek wrote:
> On Fri, Jan 13, 2012 at 07:40:59PM +0100, Georg-Johann Lay wrote:
>> The ilp32 is the closes match:
>>
>> The source casts pointer to int, int to pointer, long to int, uses 32-bit
>> initializers for int, assumes size_t is unsigned long any maybe others.
>
> No. The source
On Fri, Jan 13, 2012 at 07:40:59PM +0100, Georg-Johann Lay wrote:
> The ilp32 is the closes match:
>
> The source casts pointer to int, int to pointer, long to int, uses 32-bit
> initializers for int, assumes size_t is unsigned long any maybe others.
No. The source is just fine for any target wh
Mike Stump wrote:
> On Jan 13, 2012, at 9:23 AM, Rainer Orth wrote:
>> Mike Stump writes:
>>
>>> On Jan 13, 2012, at 4:33 AM, Georg-Johann Lay wrote:
This test case is obviously written for 32-bit platforms, thus added
"dg-require-effective-target ilp32" to ensure that the pointer mess w
On Jan 13, 2012, at 9:23 AM, Rainer Orth wrote:
> Mike Stump writes:
>
>> On Jan 13, 2012, at 4:33 AM, Georg-Johann Lay wrote:
>>> This test case is obviously written for 32-bit platforms, thus added
>>> "dg-require-effective-target ilp32" to ensure that the pointer mess won't
>>> lead
>>> to FA
Mike Stump writes:
> On Jan 13, 2012, at 4:33 AM, Georg-Johann Lay wrote:
>> This test case is obviously written for 32-bit platforms, thus added
>> "dg-require-effective-target ilp32" to ensure that the pointer mess won't
>> lead
>> to FAILs because of
>>
>> warning: cast to pointer from integ
On Jan 13, 2012, at 4:33 AM, Georg-Johann Lay wrote:
> This test case is obviously written for 32-bit platforms, thus added
> "dg-require-effective-target ilp32" to ensure that the pointer mess won't lead
> to FAILs because of
>
> warning: cast to pointer from integer of different size
>
> and
>
This test case is obviously written for 32-bit platforms, thus added
"dg-require-effective-target ilp32" to ensure that the pointer mess won't lead
to FAILs because of
warning: cast to pointer from integer of different size
and
warning: cast from pointer to integer of different size
Ok to apply
16 matches
Mail list logo
