Ulrich,
> ChangeLog:
>
> * lib/target-supports.exp (check_effective_target_mmap): Use
> check_function_available.
Ok, thanks.
Rainer
--
-
Rainer Orth, Center for Biotechnology, Bielefeld University
Rainer Orth wrote:
> sure, that's one of the reasons to centralize the mmap test. Simply
> replacing the body of the proc with
>
> return [check_function_available "mmap"]
>
> should work. Could you give it a try?
Yes, this does work for me.
Thanks,
Ulrich
ChangeLog:
* lib/tar
Ulrich,
> Rainer Orth wrote:
>
>> +proc check_effective_target_mmap {} {
>> +return [check_no_compiler_messages mmap assembly {
>> +#include
>> +}]
>> +}
>
> Unfortunately, this test breaks spu-elf; a lot of tests now fail with:
> loop-2f.c:(.text+0x100): undefined reference to `mmap'
Rainer Orth wrote:
> +proc check_effective_target_mmap {} {
> +return [check_no_compiler_messages mmap assembly {
> + #include
> +}]
> +}
Unfortunately, this test breaks spu-elf; a lot of tests now fail with:
loop-2f.c:(.text+0x100): undefined reference to `mmap'
The problem is that
Ira,
> Could this patch be also backported to 4.6? gcc.dg/vect/pr49038.c fails on
> 4.6 as well (on SPU).
I guess so. I'd like to give it two weeks soak time on mainline before
doing so.
Rainer
--
-
Rainer Ort
> When last week a testcase using mmap was posted with a copy of some old
> (and wrong) list of targets supporting mmap, I noticed what mess we have
> here. To fix this, I've introduced a new effective-target keyword mmap
> and use it in all testcases.
>
> Two minor changes to the tests were requ
When last week a testcase using mmap was posted with a copy of some old
(and wrong) list of targets supporting mmap, I noticed what mess we have
here. To fix this, I've introduced a new effective-target keyword mmap
and use it in all testcases.
Two minor changes to the tests were required:
* gcc
