RFC: Disable asan tests under ulimit -v

[Jason Merrill]

On Tue, Apr 3, 2018 at 1:23 PM, Jason Merrill <jason@redhat.com> wrote:
> On Tue, Apr 3, 2018 at 12:56 PM, Jason Merrill <jason@redhat.com> wrote:
>> On Mon, Mar 26, 2018 at 4:01 PM, Jason Merrill <jason@redhat.com> wrote:
>>>
>>> On Mon, Mar 26, 2018 at 2:55 PM, Andreas Schwab <schwab@linux-m68k.org>
>>> wrote:
>>> > On Mär 26 2018, Jakub Jelinek <jakub@redhat.com> wrote:
>>> >> On Mon, Mar 26, 2018 at 08:33:41PM +0200, Andreas Schwab wrote:
>>> >>> On Mär 26 2018, Jason Merrill <jason@redhat.com> wrote:
>>> >>>
>>> >>> >     if [catch {exec sh ulimit -v} ulimit_v] {
>>> >>>
>>> >>> expect1.1> exec sh ulimit -v
>>> >>> sh: ulimit: No such file or directory
>>> >>>     while executing
>>> >>> "exec sh ulimit -v"
>>> >>
>>> >> Perhaps
>>> >>       if [catch {exec sh -c ulimit -v} ulimit_v] {
>>> >
>>> > expect1.1> exec sh -c ulimit -v
>>> > unlimited
>>> > expect1.2> exec sh -c {ulimit -v}
>>> > 4194304
>>>
>>> OK, so
>>>
>>> if ![is_remote target] {
>>>     if [catch {exec sh -c "ulimit -v"} ulimit_v] {
>>>         # failed to get ulimit
>>>     } elseif [regexp {^[0-9]+$} $ulimit_v] {
>>>         # ulimit -v gave a numeric limit
>>>         return
>>>     }
>>> }
>>
>> This version adds a warning.  OK for trunk?

And this one puts the check in asan_init rather than its users.  OK?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: no-asan.diff
Type: text/x-patch
Size: 953 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20180411/69baaaee/attachment.bin>