This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Too much memory in chan/select2.go used

From: Ian Lance Taylor <iant at google dot com>
To: Uros Bizjak <ubizjak at gmail dot com>
Cc: gcc-patches at gcc dot gnu dot org, gofrontend-dev at googlegroups dot com
Date: Thu, 09 Feb 2012 09:44:23 -0800
Subject: Re: Too much memory in chan/select2.go used
References: <CAFULd4ai=gXSxCYXjAf24GQ-=6rYUi5eXTYvJzk2wH_Ef4ZQ_Q@mail.gmail.com> <CAFULd4bYS-jq5ZYH3+VcaKGZCMQO7WyXMR-8O07dQ7uuZFJA_A@mail.gmail.com> <mcrr4y4qzgj.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <CAFULd4asRSVZs+i-pbL8xqu_4ogLJPWFZ+-bcy44fpJ9zMKHbw@mail.gmail.com>

Uros Bizjak <ubizjak@gmail.com> writes:

> BTW: I'd like to point out that we can use go-execute-xfail in this
> case, so the case is compiled but is known to fail execution for some
> reason.

Thanks, I didn't know about that one.

I think I'll leave it as is for now because I'm treating stack.go the
same way, and stack.go does sometimes pass even without -fsplit-stack.

Ian

References:
- Too much memory in chan/select2.go used
  - From: Uros Bizjak
- Re: Too much memory in chan/select2.go used
  - From: Uros Bizjak
- Re: Too much memory in chan/select2.go used
  - From: Ian Lance Taylor
- Re: Too much memory in chan/select2.go used
  - From: Uros Bizjak

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]