. I wonder why it was necessary to disable TLSv1
completely. I can understand that weak ciphers get disabled. There are
probably some ciphers for TLSv1 that could still be allowed thus
letting older browsers access gcc.gnu.org/soureware.org.
Regards,
Gunther Nikl
Michael Meissner wrote:
> Note, the 64-bit ABI requires that r2 have the current function's GOT in it
> when the function is called, while the 32-bit ABI uses r2 as a small data
> pointer (and possibly r13 as a second small data pointer).
If the 32-bit ABI is the SYSV-ABI, then you got the registe
Bernd Roesch wrote:
a call of a function and return value with double float is on all
m68k-amigaos compiler (that use only other 68k config files but
same main source) as this.
jsr testfunc
move.l d1,-(sp)
move.l d0,-(sp)
fdmove.d (sp)+,fp1
fsmove.x fp1,fp0
lea (16,sp),sp
Bernd Roesch schrieb:
without changed headers old ompiler and libs do not work, because for C
there is no
sqrtf and other C99 funcs and many C++ programs get also many errors.
Ok, you are trying to add C99 functions to your libc. Apparently you
made a mistake if you get linker errors.
i see o
Bernd Roesch wrote:
I see in my c++config.h file
this stand here
/* Define if the compiler/host combination has __builtin_sqrtf. */
/* #undef _GLIBCXX_HAVE___BUILTIN_SQRTF */
I find now a solution that work without change of cmath
when i add in math.h this line then it work.the function can
Kai Henningsen wrote:
> On Thu, Jan 17, 2008 at 02:46:12PM -, Dave Korn wrote:
>> On 16 January 2008 22:09, Diego Novillo wrote:
>>
>>> On 1/16/08 4:16 PM, Andrew Haley wrote:
>>>
Because it's not a bug? You're changing the code to silence a false
negative, which this is what we here
On Wed, Jan 18, 2006 at 12:11:46AM +0100, Philippe De Muyter wrote:
> > GCC diffs upto 3.4.0 are available here:
> >
> >ftp://ftp.back2roots.org/pub/geekgadgets/amiga/m68k/alpha/gcc/
>
> I have downloaded them, and found the -baserel(32) and -resident(32) options.
-resident is translated to
On Tue, Jan 17, 2006 at 01:35:59PM +0100, Philippe De Muyter wrote:
> Gunther Nikl wrote :
> > On Sat, Jan 14, 2006 at 02:21:20AM +0100, Philippe De Muyter wrote:
> > > For an embedded mmu-less m68k target, I would like to generate code
> > > that will always run at a
On Sat, Jan 14, 2006 at 02:21:20AM +0100, Philippe De Muyter wrote:
> For an embedded mmu-less m68k target, I would like to generate code
> that will always run at a fixed place in memory, thus not needing to be PIC,
> but that would access a data+bss segment that could be anywhere in memory,
> thu
On Fri, Dec 23, 2005 at 04:43:09PM +0100, Paolo Bonzini wrote:
> This, in turn, is the first that is found among:
>
> 1) the default assembler (--with-as)
>
> 2) an in-tree assembler
>
> 3) AS_FOR_TARGET
>
> 4) if host == target, AS (obsolete, should be covered by case 3)
>
> 5) if build == ho
On Fri, Dec 23, 2005 at 03:50:50PM +0100, Paolo Bonzini wrote:
>
> >Wait wait wait wait wait. This is a cross compiler. Are we mistakenly
> >running $prefix/bin/$target-as, which is a bad version, or are we
> >really running $prefix/bin/as, a program named "as"? If we're doing
> >that, let's fi
On Fri, Dec 23, 2005 at 08:36:21AM -0500, Daniel Jacobowitz wrote:
> On Fri, Dec 23, 2005 at 01:19:14PM +0100, Gunther Nikl wrote:
> > Sorry for being vague, its a cross-compiler (build == host). The build
> > errors out for libgcc.a since gcc/xgcc uses the "wrong"
On Fri, Dec 23, 2005 at 01:33:30PM +0100, Paolo Bonzini wrote:
> Gunther Nikl wrote:
> >
> >If the above isn't restricted to canadian cross, it looks good. This
> >should apply for a normal cross build as well: (build == host) != target
> >
> Yes. My distinction
On Fri, Dec 23, 2005 at 10:10:01AM +0100, Paolo Bonzini wrote:
> 2) look into the --with-build-tools path, for both a Canadian cross and
> a native build. This defaults to $exec_prefix/$target/bin, so the
> default build tools (used in autoconf tests and by the being-built GCC)
> would be, if f
On Thu, Dec 22, 2005 at 11:39:20AM -0500, Daniel Jacobowitz wrote:
> On Thu, Dec 22, 2005 at 05:34:14PM +0100, Gunther Nikl wrote:
> > Hello!
> >
> > The new scheme to select target tools breaks building GCC for me. Maybe I
> > have an unusal setup. The problem in my
Hello!
The new scheme to select target tools breaks building GCC for me. Maybe I
have an unusal setup. The problem in my case is that configure now chooses
tools from $prefix/bin. It did use tools from $prefix/$target/bin before.
On my setup I have *different* tools in those places. Until know the
On Wed, Nov 30, 2005 at 10:57:42AM -0500, Daniel Berlin wrote:
> On Wed, 2005-11-30 at 16:49 +0100, Gunther Nikl wrote:
> > I retrieved gcc-2_95-branch from the svn repository and diffed it with
> > my CVS checkout. The diff contained lots of differences.
> > Many files
2/libio/stream.h
diff -x .svn -x CVS -rup ../GCC2/libio/strstream.h GCC2/libio/strstream.h
Does that indicate a major problem for the svn repository for that branch?
Thank you,
Gunther Nikl
Hello!
This PR is about missing USER_LABEL_PREFIX for static variables. The issue
was fixed for 4.0, but for 3.4 there won't be a fix as stated in the audit
trail by Mark Mitchell in comment #15. He probably based his decision on
comment #14, where Geoff Keating states that this bug does only affe
On Wed, Aug 17, 2005 at 12:33:12PM -0700, James E Wilson wrote:
> F. Heitkamp wrote:
> > a particular cpu. Looking at the specs file for the host compiler the
> > default is -mppc. When I gave the "--with-cpu=7400" shouldn't that have
> > made the default -m7400?. What about xgcc, how can I mak
On Wed, Aug 03, 2005 at 10:49:49AM -0700, Ian Lance Taylor wrote:
> Gunther Nikl <[EMAIL PROTECTED]> writes:
>
> > "Attempt to delete prologue/epilogue insn"
> >
> > unless the stackslot was marked with MEM_VOLATILE_P. I don't think thats
> >
On Wed, Aug 03, 2005 at 03:50:09PM +0100, Nathan Sidwell wrote:
> Gunther Nikl wrote:
> >I am trying to add instructions into function prologue/epilogue. These
> >instructions shall save and load "fixed" registers to avoid assembly.
> >
> >Register saving
rtx_SYMBOL_REF (Pmode, "symbol");
emit_insn (gen_elf_high (reg, ref));
emit_insn (gen_elf_low (reg, reg, ref));
How do I prevent the aborts from flow? Any help appreciated.
Gunther Nikl
On Mon, Jul 04, 2005 at 01:15:19PM +0100, Andrew Haley wrote:
> Gunther Nikl writes:
> >
> > Sometimes I use -Wl,-r and I tried to change what options to pass
> > depending on -r.
>
> IMO that would be really bad. The point of "-Wl" is to pass
On Fri, Jul 01, 2005 at 03:19:28PM -0700, James E Wilson wrote:
> Gunther Nikl wrote:
> >A few LINK_SPEC definitions contain a "%{Wl,*:%*}" sequence.
>
> There is no need to match -Wl options in LINK_SPEC, as it is handled by
> the gcc.c driver. The driver suppor
Hello!
A few LINK_SPEC definitions contain a "%{Wl,*:%*}" sequence. AFAICT this
sequence doesn't have any effect since at least GCC 2.95, because gcc.c
doesn't recored "-Wl" options in array "switch" (used in process_brace_body)
but stores them in "infiles". Should it be possible to match against
On Wed, Apr 27, 2005 at 04:40:29PM -0700, Zack Weinberg wrote:
> Daniel Berlin <[EMAIL PROTECTED]> writes:
>
> > On Wed, 2005-04-27 at 15:13 -0700, Stan Shebs wrote:
> >> Steven Bosscher wrote:
> >> >If someone had cared about them, it would have been noticed
> >> >earlier. But since _nobody_ has
On Wed, Apr 27, 2005 at 08:05:39AM -0700, Matt Thomas wrote:
> Am I the only person who has attempted to do a native bootstrap on a
> system as slow as a M68k?
I am using an Amiga with [EMAIL PROTECTED] myself. My last GCC bootstrap on
that machine was done in 1999 for GCC 2.95.2 and it took s
28 matches
Mail list logo
