On Sun, Jul 19, 2009 at 8:18 AM, Revital1 Eres wrote:
>
> Hello,
>
> The following snippet is from a f90 program which contains
> a loop that does not get vectorized.
>
> SUBROUTINE foo1(nx,ny,nz,arr2)
> USE globalvar_mod, ONLY : dyinv, xstart, xstop
>
> k=1
> do j=1,ny
> do i=1,nx
>
> arr1(i,j
Hello,
> The testcase is from 459.GemsFDTD, right? dyinv is a regular
> global variable. The issue is the global arrays arr1 and arr2 end
> up pointing to anything even though the Fortran aliasing rules say
> the do not.
Yes, the testcase is from 459.GemsFDTD.
> We are working on this issue.
2009/7/18 Andrew Pinski :
> On Sat, Jul 18, 2009 at 12:22 PM, Kai Tietz wrote:
>> Well, uintptr_t/intptr_t are available to most (but not all hosts).
>> IIRC there is a gcc version of stdint.h (gstdint.h), which could be
>> used here. The mode version is fine too, as long as we can assume that
>> l
Kai Tietz wrote:
> There are a lot of issues about casting HANDLE values into jint types,
> which is for x86 valid, but for x64 can lead potential to pointer
> truncations. Those part need some review by libjava maintainers. My
> patch simply casts those kind of pointers via __UINTPTR_TYPE__ into
2009/7/19 Dave Korn :
> Kai Tietz wrote:
>
>> There are a lot of issues about casting HANDLE values into jint types,
>> which is for x86 valid, but for x64 can lead potential to pointer
>> truncations. Those part need some review by libjava maintainers. My
>> patch simply casts those kind of pointe
Kai Tietz wrote:
> 2009/7/19 Dave Korn :
>> Kai Tietz wrote:
>>
>>> There are a lot of issues about casting HANDLE values into jint types,
>>> which is for x86 valid, but for x64 can lead potential to pointer
>>> truncations. Those part need some review by libjava maintainers. My
>>> patch simply c
2009/7/19 Dave Korn :
> Kai Tietz wrote:
>> 2009/7/19 Dave Korn :
>>> Kai Tietz wrote:
>>>
There are a lot of issues about casting HANDLE values into jint types,
which is for x86 valid, but for x64 can lead potential to pointer
truncations. Those part need some review by libjava main
Kai Tietz wrote:
> The patch I sent here is more a head-up (and it fixes build for 32-bit
> windows builds, too).
Ok, I see the point in a headsup (but I'm not sure it was worth spending the
time to generate the patch). I take it the sole problem with the 32-bit build
is the missing natVMSecu
On 07/19/2009 02:29 PM, Dave Korn wrote:
> Kai Tietz wrote:
>
>> There are a lot of issues about casting HANDLE values into jint types,
>> which is for x86 valid, but for x64 can lead potential to pointer
>> truncations. Those part need some review by libjava maintainers. My
>> patch simply casts
Andrew Haley wrote:
>
> Yes, you can change them. Yes, they are part of an ABI. native_fd should be
> a jlong.
That's the best possible answer to our questions! Kai? I'll leave this
with you; I'm busy tracking down libffi FAILs right now.
cheers,
DaveK
Hi team,
I'd like to have some basic BZ perms if I may, so I can help out with
cygwin/win32-related PRs. I'd like to be able to assign bugs to myself (at
least ones that I created myself, depending how fine-grained it is), and
perhaps be allowed to change status on other bugs too (I occasi
On Sun, Jul 19, 2009 at 7:29 PM, Dave
Korn wrote:
>
> Hi team,
>
> I'd like to have some basic BZ perms if I may, so I can help out with
> cygwin/win32-related PRs. I'd like to be able to assign bugs to myself (at
> least ones that I created myself, depending how fine-grained it is), and
> per
2009/7/19 Dave Korn :
>
> Hi team,
>
> I'd like to have some basic BZ perms if I may, so I can help out with
> cygwin/win32-related PRs. I'd like to be able to assign bugs to myself (at
> least ones that I created myself, depending how fine-grained it is), and
> perhaps be allowed to change st
Richard Guenther wrote:
> On Sun, Jul 19, 2009 at 7:29 PM, Dave
> Korn wrote:
>>Hi team,
>>
>> I'd like to have some basic BZ perms if I may, so I can help out with
>> cygwin/win32-related PRs. I'd like to be able to assign bugs to myself (at
>> least ones that I created myself, depending how
Hi, Frank
>Those in turn
>might be represented with almost the normal mf_xform_decls(), while
>letting __builtin_alloca() remain.
How can we just remain __builtin_alloca() only for variable-length array?
Mudflap changes expand_builtin_alloca function.
I think it is enough for apply mudflap in Linu
Snapshot gcc-4.3-20090719 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.3-20090719/
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
2009/7/18 Ian Lance Taylor :
> Mohamed Shafi writes:
>
>> The change logs says that current_function_outgoing_args_size is no
>> more available. But it doesnt say with what it is replaced. Looking at
>> the other targets i find that its replaced with some field in a
>> structure crtl. Where is thi
17 matches
Mail list logo