From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id E46F3385843B for ; Thu, 2 Sep 2021 14:33:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E46F3385843B Received: from mail-qt1-f199.google.com (mail-qt1-f199.google.com [209.85.160.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-549-KfFLQhSzPYS7SIsKsxMA_A-1; Thu, 02 Sep 2021 10:33:43 -0400 X-MC-Unique: KfFLQhSzPYS7SIsKsxMA_A-1 Received: by mail-qt1-f199.google.com with SMTP id t2-20020ac87382000000b002a0c1c918c3so925004qtp.13 for ; Thu, 02 Sep 2021 07:33:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=hCKvUocrAGfNqbvNN5+Ta+p5s1ZkJz1tZ0rBYFkE8t4=; b=Ijqfo4JRjHd14VWYMdtHci7Pxnfvo6aK/vrXvL1wIaLRW/OeC3kKC59gX+VZcGuxaz kDFhP2lghDlptJ6dQhZcYpUA1A/mNLfNbPBroe0fOSyrtxzIL7OQIo5xn7umHfNCwKk0 35qgH3d8XBlIRkzePUPSy9XgrgDWZPvMGg+XOl0TCp5FreLY6j1MgPq4eHSrJkbS6Eva WArjn41+N67rI2/AlBpQ+RXzIWcsQ3b54AvT40Dyz67eQkVJGWqMV7Bvl177D0/ZJUAa 6tmqgph3wUPR4wD0hh3//iVZ0BJzHG0XpdzUuvO9W9lonNXXZu0jowuavuu03E9uFu7l duWA== X-Gm-Message-State: AOAM533gwRhuwuT+iQ9Y7AePZCi3Wdq8z0yxvVzR+HbnzdzwY4yIcOur uDmhHv8cOhEmOmArK4ZKV8Hi9SHNap9ufu9yJZbEmdF6pDBwnn4YcMDi52VZcQsoKzxScA540S5 akpp/FFg= X-Received: by 2002:a37:a883:: with SMTP id r125mr3363607qke.408.1630593222803; Thu, 02 Sep 2021 07:33:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxfzadT1v8UC5jQ+j3oo3YY774u5h6lGSvGuv+MlJYnU4lBQMhKBDREuexD9oYwrwj1dMGoQQ== X-Received: by 2002:a37:a883:: with SMTP id r125mr3363590qke.408.1630593222598; Thu, 02 Sep 2021 07:33:42 -0700 (PDT) Received: from t14s.localdomain (c-73-69-212-193.hsd1.ma.comcast.net. [73.69.212.193]) by smtp.gmail.com with ESMTPSA id u22sm1516788qkj.123.2021.09.02.07.33.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Sep 2021 07:33:42 -0700 (PDT) Message-ID: <3ce0d8336fb7290d7a1dfcade0b2104dd3efcc77.camel@redhat.com> Subject: Re: Global register variables From: David Malcolm To: Marc =?ISO-8859-1?Q?Nieper-Wi=DFkirchen?= , jit@gcc.gnu.org Date: Thu, 02 Sep 2021 10:33:40 -0400 In-Reply-To: References: User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: jit@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Jit mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Sep 2021 14:33:46 -0000 On Tue, 2021-08-31 at 08:39 +0200, Marc Nieper-Wißkirchen via Jit wrote: > Does libgccjit support GCC's global register variables ([1])? Not currently. > > If not, could we expect them to be included?   > One major use case of > libgccjit seems to be JIT compilation of some virtual machine bytecode > and > virtual machines usually need a number of global variables (like some > virtual stack pointer or heap pointer, etc.).  It makes a lot of sense > to > hold them in global (callee-saved) registers. Sounds like a useful feature; if someone wants to cook up a patch I can review it. Dave