Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > The following patch automatically enables 64-bit mode on AMD opteron.
> > We already had spinlock support for it, but I added some comments.
>
> This sort of thing belongs into the template file, not directly in
> configure.in.
I knew you wer
Bruce Momjian writes:
> The following patch automatically enables 64-bit mode on AMD opteron.
> We already had spinlock support for it, but I added some comments.
This sort of thing belongs into the template file, not directly in
configure.in.
--
Peter Eisentraut [EMAIL PROTECTED]
--
Manfred Spraul wrote:
> Bruce Momjian wrote:
>
> > if test "$enable_debug" = yes && test "$ac_cv_prog_cc_g" = yes; then
> >CFLAGS="$CFLAGS -g"
> > fi
> >+
> >+ /* Compile AMD Opteron using gcc in 64-bit mode */
> >+ if test "$GCC" = yes; then
> >+ case $host in
> >+ ia64-*) CFLAGS="$CFLA
Bruce Momjian wrote:
if test "$enable_debug" = yes && test "$ac_cv_prog_cc_g" = yes; then
CFLAGS="$CFLAGS -g"
fi
+
+ /* Compile AMD Opteron using gcc in 64-bit mode */
+ if test "$GCC" = yes; then
+ case $host in
+ ia64-*) CFLAGS="$CFLAGS -m64"
+LDFLAGS="$LDFLAGS -melf_x86_64"
The following patch automatically enables 64-bit mode on AMD opteron.
We already had spinlock support for it, but I added some comments.
The big question is whether all the operating systems running gcc on
Opteron support the 64-bit flags, and if we want to enable them by
default on Opteron.
If
Interesting. The compiler doesn't do x86_64 by default --- you have to
enable it in the compile.
Any idea how to handle this in our builds? It doesn't seem like a
property of the OS as much as a property of the compiler --- we
already do 64-bit on some platforms without flags.
What is the full
The s_lock.h change will be in 7.4.
---
Tom Lane wrote:
> "Martin D. Weinberg" <[EMAIL PROTECTED]> writes:
> > I didn't change the source tree at all. I used:
>
> > env CFLAGS='-O3 -m64' LD='/usr/bin/ld -melf_x86_64' ./con
