Jeff Law via Gcc-patches writes:
> I'm not really sure we need a patch for this. Isn't it sufficient to
> "make all-gcc && make all-target-libgcc"? Folks have been doing that
> for decades.
>
> Jeff
Oh, I did not know that "make install-gcc install-target-libgcc" works in this
case.
So in
Final ping before stage3 ends:
[PATCH] Add --enable-first-stage-cross configure option
https://gcc.gnu.org/pipermail/gcc-patches/2021-July/575318.html
Ping: [PATCH] Add --enable-first-stage-cross configure option
https://gcc.gnu.org/pipermail/gcc-patches/2021-July/575318.html
Add --enable-first-stage-cross configure option
Build static-only, C-only compiler that is sufficient to cross compile
glibc. This option disables various runtime
Ping?
[PATCH] Add --enable-first-stage-cross configure option
https://gcc.gnu.org/pipermail/gcc-patches/2021-July/575318.html
> Add --enable-first-stage-cross configure option
>
> Build static-only, C-only compiler that is sufficient to cross compile
> glibc. This option disables various
Jakub Jelinek writes:
> On Mon, Sep 06, 2021 at 12:49:18PM +0300, Serge Belyshev wrote:
> * gcc_update: derive human readable name for HEAD using git describe
>
> After : start with upper case, ^^^ Derive
>
> like "git gcc-descr" with short commit hash.
Ping?
[PATCH v3] gcc_update: use human readable name for revision string in
gcc/REVISION
https://gcc.gnu.org/pipermail/gcc-patches/2021-July/575556.html
>
> OK for mainline?
>
> ---
> contrib/Changelog:
>
> * gcc_update: derive human readable name for HEAD using git describe
> like
Jeff Law writes:
> This set is approved. Push them to the trunk when it's convenient
> for you.
>
> Thanks for your patience,
Thanks! Committed as r12-3047 .. r12-3050.
Jeff Law writes:
> On 7/20/2021 9:44 AM, Serge Belyshev wrote:
>> Special-casing checks for in-tree gas features is unnecessary since
>> r17 which made configure-gcc depend on all-gas, and thus making
>> alternate code path in gcc_GAS_CHECK_FEATURE for in-tree gas
>
configure: remove gas versions from tls check
gcc/ChangeLog:
* configure.ac (thread-local storage support): Remove tls_first_major
and tls_first_minor. Use "$conftest_s" to check support.
* configure: Regenerate.
---
gcc/configure| 58
configure: fixup formatting from previous change
gcc/ChangeLog:
* configure.ac: Fixup formatting.
---
gcc/configure.ac | 71 ++--
1 file changed, 27 insertions(+), 44 deletions(-)
diff --git a/gcc/configure.ac b/gcc/configure.ac
index
configure: remove version argument from gcc_GAS_CHECK_FEATURE
gcc/ChangeLog:
* acinclude.m4 (gcc_GAS_CHECK_FEATURE): Remove third argument and ...
* configure.ac: ... update all callers.
---
gcc/acinclude.m4 | 16 ++--
gcc/configure.ac | 224
configure: drop version checks for in-tree gas [PR91602]
gcc/ChangeLog:
PR build/91602
* acinclude.m4 (_gcc_COMPUTE_GAS_VERSION, _gcc_GAS_VERSION_GTE_IFELSE)
(gcc_GAS_VERSION_GTE_IFELSE): Remove.
(gcc_GAS_CHECK_FEATURE): Do not handle in-tree case specially.
-sun-solaris2.11 and powerpc-ibm-aix7.{1.5.0,2.4.0}, with and without
in-tree binutils (except on aix where combined tree does not appear to work
due to dynamic linker peculiarity).
OK for mainline ?
Serge Belyshev (4):
configure: drop version checks for in-tree gas [PR91602]
configure: remove
>> > On 19 Jul 2021, at 11:39, Richard Biener via Gcc-patches
>> > wrote:
>> >
>> > On Fri, Jul 16, 2021 at 12:37 PM Serge Belyshev
>> > wrote:
>> >>
>> >> Based on discussion I've chosen open-coded version without commit
Based on discussion I've chosen open-coded version without commit hash.
>> > > ... Perhaps rename the r, o, rr and m temporaries.
I like it better with short names, there is no other code in that
script to clash with. (Also, two adjacent case branches for hg and svn
are essentialy dead now).
This is to make development version string more readable, and
to simplify navigation through gcc-testresults.
Currently gcc_update uses git log --pretty=tformat:%p:%t:%H to
generate version string, which is somewhat excessive since conversion
to git because commit hashes are now stable.
Even
Add --enable-first-stage-cross configure option
Build static-only, C-only compiler that is sufficient to cross compile
glibc. This option disables various runtime libraries that require
libc to compile, turns on --with-newlib, --without-headers,
--disable-decimal-float, --disable-shared,
2021-05-17 Serge Belyshev
* MAINTAINERS (Write After Approval): Add myself.
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5b10f212ce8..fbaa183cea4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -317,6 +317,7 @@ Gergö Barany
> $ egrep "mpfr\.h" log/cfg/cfg.gcc-11.1.0.log
> checking for the correct version of mpfr.h... buggy but acceptable
>
> It appears "gcc-11.1.0/contrib/download_prerequisites"
> specifies "mpfr-3.1.4.tar.bz2" whereas top level 'configure'
> has "MPFR_VERSION_NUM(3,1,6)".
>
> Is there a reason
> My builds for the last couple of days have all been failing in stage 2
> like so:
>
> /home/arth/src/gcc/gcc/config/i386/i386.c: In function ‘rtx_def*
> ix86_expand_bui
> ltin(tree, rtx, rtx, machine_mode, int)’:
> /home/arth/src/gcc/gcc/config/i386/i386.c:38407:18: error: ‘fcn’ may be used
>
Andrew Pinski pins...@gmail.com writes:
On Fri, Apr 1, 2011 at 8:57 PM, Alex cirru...@uol.com.br wrote:
If I understood correct, gcc could replace insns 5, 7, 8 and 9 by the insn
defined as *andmode_2, but it seems combine did not tried that.
Yes you missed that combine in GCC only acts on
[EMAIL PROTECTED] writes:
Over the previous years, I had downloaded and used both a really archaic
gcc-1.09 DLX backend as well as the one you refer too. They are both in a sad
state of affairs, but the gcc-2.7.2.1 (AFAICR) was usable.
Offtopic: if you still have such an old gcc-1.09 (?)
Toon Moene [EMAIL PROTECTED] writes:
L.S.,
Recently, I've begun to bootstrap with make BOOT_CFLAGS=flags,
basically to get the run time libraries (libgfortran, libgomp)
compiled with -mcpu=native -mtune=native (the speed of the compiler
doesn't interest me that much).
However, I see that
Andreas Jaeger [EMAIL PROTECTED] writes:
bootstrap with current svn head fails for me on Linux/x86-64:
...
cc1: warnings being treated as errors
/cvs/gcc-svn/trunk/gcc/treelang/treetree.c:1191: error:
‘treelang_expand_function’ defined but not used
make[3]: *** [treelang/treetree.o] Error 1
Richard Guenther [EMAIL PROTECTED] writes:
It was a patch to enable more optimization. Reverting it should be as safe
or unsafe as exchanging forwprop and dce passes. And I have no idea
as how to quantify safeness of either ;)
I'd say we better analyze what goes wrong (as the problem is
Vladimir N. Makarov [EMAIL PROTECTED] writes:
I run SPEC2000 several times per week and always look at 3 runs (to be
sure that is nothing wrong happened) but I never saw such big
confidence intervals (as I understand that is difference between max
and min of 3 runs divided by the score).
I have compared 4.1.2 release (r121943) with three revisions of 4.2 on spec2k
on an 2GHz AMD Athlon64 box (in 64bit mode), detailed results are below.
In short, current 4.2 performs just as good as 4.1 on this target
with the exception of huge 80% win on 178.galgel. All other difference
lies
Steven Bosscher [EMAIL PROTECTED] writes:
Hello,
...[snip]
So I'm looking for help here: Who can help me find a test case to trigger
a verify_flow_info ICE in GCC with the above patch applied? Can people
try this patch on their favorite target, and see if they can trigger a
test suite
Gabriel Dos Reis [EMAIL PROTECTED] writes:
Gerald Pfeifer [EMAIL PROTECTED] writes:
| On Sun, 28 Jan 2007, Joe Buck wrote:
| It's probably time to turn off 4.0 snapshots; the last ones will
| probably be Gaby's prerelease snapshots, and the release should come
| soon.
|
| That's a
29 matches
Mail list logo
