public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <idsandoe@googlemail.com>
To: Shengyu Huang <kumom.huang@gmail.com>
Cc: David Malcolm <dmalcolm@redhat.com>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on
Date: Mon, 27 Feb 2023 13:45:33 +0000	[thread overview]
Message-ID: <572CCB25-4FA0-49C4-92CD-0ED07F910DDD@googlemail.com> (raw)
In-Reply-To: <86EF7DED-439B-4B43-9E0D-425CC4010495@gmail.com>

Hi Shengyu

> On 27 Feb 2023, at 13:35, Shengyu Huang via Gcc <gcc@gcc.gnu.org> wrote:

> Sorry for the late reply. I just built gcc-12-2 on my machine with bootstrap and it worked.

great,
> 
> However, maybe due to some missing configuration, building without bootstrap does not work on my machine (development branch or gcc-12-2). Specifically, my configuration is as follows.
> 
> ```
> $HOME/dropbox/projects/gcc-darwin-arm64/configure --disable-bootstrap --with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk --prefix=$PWD
> ```

Please file an issue against the branch on github (since this is a development branch it’s not appropriate to use the GCC bugzilla yet).

I think that there is at least one known issue with non-bootstrap builds (to do with flags not recognised by clang) but not sure, yet, if this is the same case.

In general, if you want to build without boostrapping [as is often the case with development] then the best thing to do is to bootstrap a recent compiler [or the unmodified sources] and then use that GCC as your build compiler (this ensures you have compatible flags and builtins).

thanks
Iain


  reply	other threads:[~2023-02-27 13:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 21:26 Shengyu Huang
2023-02-21 22:55 ` David Malcolm
2023-02-22 14:03   ` Jonathan Wakely
2023-02-23 11:17     ` James K. Lowden
2023-02-23 16:30       ` Jonathan Wakely
2023-02-22 14:11   ` Shengyu Huang
2023-02-22 14:53     ` Iain Sandoe
2023-02-22 15:13       ` Iain Sandoe
2023-02-27 13:35       ` Shengyu Huang
2023-02-27 13:45         ` Iain Sandoe [this message]
2023-02-27 13:51           ` Shengyu Huang
2023-02-27 13:49         ` Iain Sandoe
2023-02-27 14:01           ` Floyd, Paul
2023-02-22 15:43     ` David Malcolm
2023-02-28  9:18       ` Shengyu Huang
2023-02-28 23:59         ` David Malcolm
2023-03-01 11:16           ` Shengyu Huang
2023-03-01 13:48             ` David Malcolm
2023-02-28 14:46     ` [GSoC][Static Analyzer] Ideas for proposal Shengyu Huang
2023-03-01  0:22       ` David Malcolm
2023-03-12 22:20         ` Shengyu Huang
2023-03-13 15:51           ` David Malcolm
2023-03-20 17:28             ` [GSoC][Static Analyzer] First proposal draft and a few more questions/requests Shengyu Huang
2023-03-20 22:50               ` David Malcolm
2023-03-26 16:03                 ` Shengyu Huang
2023-03-26 17:14                   ` David Malcolm
2023-03-26 21:46                     ` Shengyu Huang
2023-04-01 14:19                       ` Shengyu Huang
2023-04-02 22:53                         ` David Malcolm
2023-04-03  0:02                           ` Shengyu Huang

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=572CCB25-4FA0-49C4-92CD-0ED07F910DDD@googlemail.com \
    --to=idsandoe@googlemail.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kumom.huang@gmail.com \
    /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: link
Be 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).