Hi,
I'm observing the following bootstrap problem with mainline in
i686-pc-linux-gnu:
the initial ./configure dies with:
[...]
checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1
$$f2
checking for correct version of gmp.h... yes
checking for MPFR... yes
configure: erro
Martin Reinecke wrote:
Hi,
I'm observing the following bootstrap problem with mainline in
i686-pc-linux-gnu:
the initial ./configure dies with:
[...]
checking how to compare bootstrapped objects... cmp --ignore-initial=16
$$f1 $$f2
checking for correct version of gmp.h... yes
checking for M
I can no longer configure/build GCC with Ada enabled after your change:
r115145 | bonzini | 2006-07-03 09:58:08 +0200 (Mon, 03 Jul 2006) | 24 lines
2006-07-03 Paolo Bonzini <[EMAIL PROTECTED]>
PR other/27063
* configure.in: Test subdir_requires and give an appropriate
e
On Mon, 2006-07-03 at 02:10, Bridge Wu wrote:
> Hello,
>
> When I built blob with arm-iwmmxt-linux-gnueabi toolchain, I found the
> SP value before invoking number() in printf() may be 0 or 4 modulo 8.
> If SP is 0 modulo 8, printf worked well, but while SP is 4 modulo 8,
> printf failed. It canno
Seongbae Park wrote:
> As I said, you're welcome to implement a new option
> (either a runtime option or a compile time configuration option)
> that will allow mixing TLS vs non-TLS.
In a way, we've already done that -- in an experimental dialact of "C"
called UPC. When compiled for pthreads, al
On 7/3/06, Gary Funck <[EMAIL PROTECTED]> wrote:
Seongbae Park wrote:
> As I said, you're welcome to implement a new option
> (either a runtime option or a compile time configuration option)
> that will allow mixing TLS vs non-TLS.
In a way, we've already done that -- in an experimental dialact
Seongbae Park wrote:
> In UPC, anything that's not TLS (or in UPC term, "private")
> is marked explicitly as "shared". So it's NOT trasparent in
> any sense of the word.
> See, you have two choices - either
> 1) make every global variable TLS by default and mark only
> non-TLS (UPC) or
> 2) vice
On 7/3/06, Gary Funck <[EMAIL PROTECTED]> wrote:
...
Operations on UPC's shared objects have different semantics than
regular "C". Array indexing and pointer operations span threads.
Thus A[i] is on one thread but A[i] will (by default) take you to
the next (cyclic) thread. Since the semant
