cbb-gcc-4.6.4 - compiler building blocks: cbb-gcc-4.6.4: including full support for the midipix targets

Age	Commit message (Collapse)	Author	Files	Lines
2015-03-27	gcc/config/i386/driver-i386.c: replace 'asm' with '__asm__' since	midipix	1	-1/+1
	the former does not allow passing -std=... as a compiler flag. signed-off by Z. Gilboa; see copying.midipix (9cd0746c) for additional information.
2015-03-26	midipix.h: define HOST_EXECUTABLE_SUFFIX to be a null string.	midipix	1	-0/+3
	signed-off by Z. Gilboa; see copying.midipix (9cd0746c) for additional information.
2015-03-21	midipix target implementation: initial commit.	midipix	8	-0/+1127
	signed-off by Z. Gilboa; see copying.midipix (9cd0746c) for additional information.
2015-03-20	gcc/config: add empty headers files to satisfy build system requirements.	midipix	2	-0/+2
	signed-off by Z. Gilboa; see copying.midipix (9cd0746c) for additional information.
2015-03-20	gcc/config: (continue to) make the os-specific headers libc-agnostic.	midipix	2	-143/+0
	+ remove gnu.h and gnu-user.h, as they are no longer needed. + this patch continues the work started in 41b5093c. signed-off by Z. Gilboa; see copying.midipix (9cd0746c) for additional information.
2015-03-18	gcc/config/linux.h: add an empty header file to satisfy build system ↵	midipix	1	-0/+1
	requirements. signed-off by Z. Gilboa; see copying.midipix (9cd0746c) for additional information.
2015-03-18	linux: i386/x86_64: make the os-specific headers libc-agnostic.	midipix	3	-189/+0
	+ libc-specific definitions should now be provided in dedicated headers, for instance by adding --include=libc-defs.h to the relevant compiler flags. signed-off by Z. Gilboa; see copying.midipix (9cd0746c) for additional information.
2015-03-15	obtained gcc-4.6.4.tar.bz2 from upstream website;upstream	upstream source tree	1540	-0/+859149
	verified gcc-4.6.4.tar.bz2.sig; imported gcc-4.6.4 source tree from verified upstream tarball. downloading a git-generated archive based on the 'upstream' tag should provide you with a source tree that is binary identical to the one extracted from the above tarball. if you have obtained the source via the command 'git clone', however, do note that line-endings of files in your working directory might differ from line-endings of the respective files in the upstream repository.