This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libcc1



On 10/29/2014 11:45 AM, Jakub Jelinek wrote:
> On Wed, Oct 29, 2014 at 11:37:26AM +0100, Paolo Bonzini wrote:
>> On 10/29/2014 11:31 AM, Jakub Jelinek wrote:
>>> shouldn't libcc1 be in build_tools instead?
>>> I mean, it is a library meant to be dlopened by gdb and gcc
>>> plugin that uses that library, so in canadian-cross should be
>>> for the build target, where the resulting compiler will be run
>>> and where gdb will be run.
>>
>> That is host, not build.  Build is the system you are on.
> 
> Oops, sorry, mixed that, sure, it should be host tool then.
> 
> So without the first two hunks and third hunk changed so that it
> doesn't bootstrap it?  Doesn't that mean that when bootstrapping
> natively it will be built by the system compiler rather than the
> newly built compiler?

IIRC it will be built after stage3 completes, with the just-bootstrapped
compiler.

> I think fixincludes is only built during
> stage1 normally, we don't need libcc1 during stage1/stage2 unless
> not bootstrapping, it is needed just for installation and testing.
> 
> --- configure.ac	2014-10-28 14:39:53.018852391 +0100
> +++ configure.ac	2014-10-29 11:43:19.873216226 +0100
> @@ -2677,6 +2677,7 @@ for module in ${configdirs} ; do
>    fi
>    case ${module},${bootstrap_fixincludes} in
>      fixincludes,no) host_bootstrap_suffix=no-bootstrap ;;
> +    libcc1,*) host_bootstrap_suffix=no-bootstrap ;;
>      *) host_bootstrap_suffix=$bootstrap_suffix ;;
>    esac
>    extrasub_host="$extrasub_host

This makes sense.

Paolo


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]