avr-libc-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[avr-libc-dev] required patches for avr-gcc 4.3.0


From: Rolf Ebert
Subject: [avr-libc-dev] required patches for avr-gcc 4.3.0
Date: Mon, 11 Feb 2008 23:13:11 +0100
User-agent: Thunderbird 2.0.0.9 (Windows/20071031)

Weddington, Eric schrieb:
I was wondering if it is worth to get all the patches cleanly apply to 4.2.3 or if the effort is better invested in porting the patches to the upcoming 4.3.0.


My suggestion then, is to focus on getting 4.3.0 in shape for avr-ada,



From the list of patches in winavr/patches/gcc/4.2.2/* the following patches

- are still needed and can be applied directly:
20-gcc-4.2.2-libiberty-Makefile.in.patch
41-gcc-4.2.2-bug-10768.patch
42-gcc-4.2.2-bug-30243.patch
60-gcc-4.2.2-ada-xgnatugn.patch

- are not needed anymore:
00-gcc-4.2.2-version-WinAVR.patch (is now an option to the configure script)
10-gcc-4.2.2-c-incpath.patch
22-gcc-4.2.2-objc.patch
30-gcc-4.2.2-binary-constants.patch
31-gcc-4.2.2-relax.patch
32-gcc-4.2.2-os_main_os_task_v2.patch
33-gcc-4.2.2-constraint-desc.patch
34-gcc-4.2.2-doc-progmem.patch
35-gcc-4.2.2-zero_extend.patch
51-gcc-4.2.2-at90pwmx16.patch
52-gcc-4.2.2-attiny43u.patch
53-gcc-4.2.2-attiny48.patch
54-gcc-4.2.2-at90pwm2b3b.patch
55-gcc-4.2.2-atmega48p-88p-168p-328p.patch
56-gcc-4.2.2-remove-devices.patch
57-gcc-4.2.2-attiny88.patch
58-gcc-4.2.2-atmega1284p.patch
59-gcc-4.2.2-atmega32hvb.patch
59-gcc-4.2.2-avr35.patch

- need porting to 4.3
11-gcc-4.2.2-exec-prefix.patch (not sure, it seems a different solution is already applied)
21-gcc-4.2.2-disable-libssp.patch
23-gcc-4.2.2-ada-Makefile.patch
43-gcc-4.2.2-bug-11259-v2.patch
50-gcc-4.2.2-mega256-v3.patch
61-gcc-4.2.2-ada-freestanding.patch
62-gcc-4.2.2-ada-mlib.patch
63-gcc-4.2.2-ada-timebase.patch
64-gcc-4.2.2-ada-gnat1_print_path.patch

------------------------------------------------------------

I hope this information helps anybody who dares to build a gcc-4.3 based compiler.

    Rolf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]