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]

Re: gen-num-limits runs forever on GNU/Linux/sparc (Red Hat Linux 6.2)


Alexandre Oliva <aoliva@redhat.com> writes:

| On Feb  1, 2001, Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr> wrote:
| 
| > Alexandre Oliva <aoliva@redhat.com> writes:
| > | On Feb  1, 2001, Gabriel Dos Reis <gdr@codesourcery.com> wrote:
| > | 
| > | > Alexandre Oliva <aoliva@redhat.com> writes:
| > | 
| > | > [...]
| > | 
| > | > | Tested on sparc-unknown-linux-gnu, with and without -DHAVE_SIGSETJMP.
| > | > | The latter compiled, but would never complete, as before.  Ok to
| > | > | install?
| > | 
| > | > Alexandre, can't it be possible to detect HAVE_SIGSETJUMP through
| > | > autoconf?  I would prefer an autocoonf-based solution.
| > | 
| > | Well...  Sure it is.  I just didn't think it was worth the trouble.
| > | We'd have to start #including <config.h> in gen-num-limits.cc, for
| > | one.
| 
| > Hmm, I think at some point, gen-num-limits.cc (which needs a clean up)
| > would require more collaboration from the compiler, so #including a
| > <config.h> isn't a big deal.
| 
| And the other problem is that mknumeric_limits runs before config.h is
| built :-)

In the case of mknumeric_limits we _just_ need to test for
`sigsetjump', we should not have to wait until the completion of
totality of the features we test for.

| Well, confdefs.h could do instead...

That would be sufficient.

| Or we could delay the execution of mknumeric_limits to a Makefile
| rule.  Thoughts?

I would like we keep running mknumeric_limits at confiigure-time.

-- Gaby
CodeSourcery, LLC                       http://www.codesourcery.com

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