public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/100486] Ada build fails for 32bit Windows Date: Sun, 04 Jul 2021 09:10:06 +0000 [thread overview] Message-ID: <bug-100486-4-EmeoLESjGd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100486-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100486 --- Comment #8 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > make BOOT_CFLAGS='-O1' V=1 all > > make BOOT_CFLAGS='-O0' V=1 > > both fails the same way as the initial report. That's not what I was asking for though, BOOT_CFLAGS should generally not be fiddled with. > Finally, trying to reduce as much as possible the optimization passes: > > export CFLAGS="-march=i686 -mtune=generic -Og -pipe" > export CXXFLAGS="-march=i686 -mtune=generic -Og -pipe" > make BOOT_CFLAGS='-Og' V=1 What happens if you do not set any of CFLAGS/CXXFLAGS/BOOT_CFLAGS?
next prev parent reply other threads:[~2021-07-04 9:10 UTC|newest] Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-08 12:22 [Bug ada/100486] New: " reiter.christoph at gmail dot com 2021-05-08 14:26 ` [Bug ada/100486] " ebotcazou at gcc dot gnu.org 2021-05-10 20:30 ` ofv at wanadoo dot es 2021-07-02 8:36 ` ebotcazou at gcc dot gnu.org 2021-07-03 3:42 ` ofv at wanadoo dot es 2021-07-03 3:58 ` ofv at wanadoo dot es 2021-07-03 7:27 ` ebotcazou at gcc dot gnu.org 2021-07-03 23:14 ` ofv at wanadoo dot es 2021-07-04 9:10 ` ebotcazou at gcc dot gnu.org [this message] 2021-07-04 13:39 ` ofv at wanadoo dot es 2021-07-04 14:43 ` ofv at wanadoo dot es 2021-07-04 17:15 ` ebotcazou at gcc dot gnu.org 2021-07-04 18:35 ` ofv at wanadoo dot es 2021-07-05 8:59 ` ralphengels at gmail dot com 2021-07-28 9:02 ` ebotcazou at gcc dot gnu.org 2021-07-30 7:49 ` reiter.christoph at gmail dot com 2021-10-10 2:41 ` gcc_bugzilla at axeitado dot com 2021-10-10 7:59 ` ebotcazou at gcc dot gnu.org 2021-10-10 16:50 ` gcc_bugzilla at axeitado dot com 2021-10-10 16:54 ` gcc_bugzilla at axeitado dot com 2021-10-11 7:51 ` ebotcazou at gcc dot gnu.org 2021-10-11 13:17 ` gcc_bugzilla at axeitado dot com 2021-10-11 14:11 ` ebotcazou at gcc dot gnu.org 2021-10-11 14:51 ` gcc_bugzilla at axeitado dot com 2021-10-11 15:05 ` gcc_bugzilla at axeitado dot com 2021-10-15 13:31 ` ebotcazou at gcc dot gnu.org 2021-10-15 14:05 ` gcc_bugzilla at axeitado dot com 2021-10-15 14:53 ` ebotcazou at gcc dot gnu.org 2021-10-15 18:55 ` ebotcazou at gcc dot gnu.org 2021-10-15 20:48 ` gcc_bugzilla at axeitado dot com 2021-10-15 21:44 ` ebotcazou at gcc dot gnu.org 2021-10-15 22:01 ` gcc_bugzilla at axeitado dot com 2021-10-15 22:50 ` ebotcazou at gcc dot gnu.org 2021-10-15 22:58 ` ebotcazou at gcc dot gnu.org 2021-10-15 23:07 ` ebotcazou at gcc dot gnu.org 2021-10-15 23:08 ` gcc_bugzilla at axeitado dot com 2021-10-15 23:12 ` gcc_bugzilla at axeitado dot com 2021-10-15 23:18 ` ebotcazou at gcc dot gnu.org 2021-10-15 23:28 ` gcc_bugzilla at axeitado dot com 2021-10-15 23:29 ` ebotcazou at gcc dot gnu.org 2021-10-15 23:30 ` ebotcazou at gcc dot gnu.org 2021-10-15 23:56 ` gcc_bugzilla at axeitado dot com 2021-10-16 0:04 ` ebotcazou at gcc dot gnu.org 2021-10-16 0:08 ` gcc_bugzilla at axeitado dot com 2021-10-16 5:19 ` reiter.christoph at gmail dot com 2021-10-16 7:55 ` ebotcazou at gcc dot gnu.org 2021-10-16 8:05 ` reiter.christoph at gmail dot com 2021-10-16 8:14 ` ebotcazou at gcc dot gnu.org 2021-10-16 8:20 ` reiter.christoph at gmail dot com 2021-10-16 8:36 ` ebotcazou at gcc dot gnu.org 2021-10-16 11:36 ` ebotcazou at gcc dot gnu.org 2021-10-16 12:33 ` reiter.christoph at gmail dot com 2021-10-16 22:09 ` reiter.christoph at gmail dot com 2021-10-17 2:17 ` gcc_bugzilla at axeitado dot com 2021-10-17 11:00 ` ebotcazou at gcc dot gnu.org 2021-10-17 13:43 ` gcc_bugzilla at axeitado dot com 2021-10-18 7:12 ` charlet at gcc dot gnu.org 2021-10-18 8:00 ` ebotcazou at gcc dot gnu.org 2021-10-18 8:05 ` ebotcazou at gcc dot gnu.org 2021-10-18 8:08 ` charlet at gcc dot gnu.org 2021-10-18 8:35 ` ebotcazou at gcc dot gnu.org 2021-10-18 8:45 ` charlet at gcc dot gnu.org 2021-10-18 10:49 ` ebotcazou at gcc dot gnu.org 2021-10-18 10:57 ` charlet at gcc dot gnu.org 2021-10-18 11:54 ` gcc_bugzilla at axeitado dot com 2021-10-18 12:43 ` ebotcazou at gcc dot gnu.org 2021-10-18 13:24 ` gcc_bugzilla at axeitado dot com 2021-10-18 15:18 ` ebotcazou at gcc dot gnu.org 2021-10-20 8:46 ` cvs-commit at gcc dot gnu.org 2021-10-20 8:47 ` cvs-commit at gcc dot gnu.org 2021-10-20 8:50 ` ebotcazou at gcc dot gnu.org 2021-10-20 17:58 ` gcc_bugzilla at axeitado dot com 2021-10-20 19:59 ` reiter.christoph at gmail dot com 2022-05-22 15:19 ` reiter.christoph at gmail dot com 2022-05-22 15:49 ` charlet at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-100486-4-EmeoLESjGd@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).