public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
	       Richard Guenther <richard.guenther@gmail.com>,
	       DJ Delorie <dj@redhat.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Attempt to increase RLIMIT_STACK in the driver as well as compiler (PR c++/49756, take 3)
Date: Fri, 22 Jul 2011 23:22:00 -0000	[thread overview]
Message-ID: <mcrhb6eq71f.fsf@coign.corp.google.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1107230003120.22948@gerinyyl> (Gerald Pfeifer's	message of "Sat, 23 Jul 2011 00:19:45 +0200 (CEST)")

Gerald Pfeifer <gerald@pfeifer.com> writes:

> That puzzled me at first, but FreeBSD defines RLIM_INFINITY in 
> /usr/include/sys/resource.h and as follows:
>
>   ((rlim_t)(((uint64_t)1 << 63) - 1))

Oy.


> 2011-07-22  Gerald Pfeifer  <gerald@pfeifer.com>
>
> 	PR target/49817
> 	* stack-limit.c: Include <stdint.h>.

This is OK.

Thanks.

Ian

      reply	other threads:[~2011-07-22 22:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 23:20 [PATCH] Attempt to increase RLIMIT_STACK in the driver as well as compiler (PR c++/49756) Jakub Jelinek
2011-07-19  8:42 ` Mike Stump
2011-07-19  8:46   ` Mike Stump
2011-07-19  8:57 ` [PATCH] Attempt to increase RLIMIT_STACK in the driver as well as compiler (PR c++/49756, take 2) Jakub Jelinek
2011-07-19 10:18   ` Richard Guenther
2011-07-21 15:19     ` [PATCH] Attempt to increase RLIMIT_STACK in the driver as well as compiler (PR c++/49756, take 3) Jakub Jelinek
2011-07-21 18:32       ` Ian Lance Taylor
2011-07-22 23:01         ` Gerald Pfeifer
2011-07-22 23:22           ` Ian Lance Taylor [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=mcrhb6eq71f.fsf@coign.corp.google.com \
    --to=iant@google.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=jakub@redhat.com \
    --cc=richard.guenther@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).