From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) by sourceware.org (Postfix) with ESMTPS id 64E92385042D for ; Thu, 19 May 2022 11:38:24 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 64E92385042D Received: by mail-ot1-x335.google.com with SMTP id m6-20020a05683023a600b0060612720715so3324867ots.10 for ; Thu, 19 May 2022 04:38:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5OrUZpb/H5EUS34BseoQJoNnUABxCcmCAG3LJkVAgZ8=; b=awSOTkhXwP05L0N/5x4t79me+A93GQJKWMmAekz75Jx+MXoGf/8QRmg/Jn4U8gDI3j ttE/3Tdqve7KNwJYgSAJObJimXFE7CbmMKtH6D+szcM3UeIdtKKEf6NTP8Z4TAkSb5A/ VIKcXs2z3wmMSd1XM7hgKJz5nyLNe8uISPWOudQSGHaAyq+WFjKGHRddoDsni29npC8J Z2V3yXKKobAjhuVXZQiEDLagWcPNUN64yzjGr6qW0hXV27gzoUyO398YUKjygyIuCwsq 8hON889ggIMgn1wKvLHy3K49Ja/cRv91hc1bixc9dUFWYozStwhVIKwquMsrDgrMXOEp S+kA== X-Gm-Message-State: AOAM530XaJSQ+UAfjXgVyeKW7K7AqNdZoOk6z22i+XAlOoGqW0BR99+Y dvsao7naAqCUFwCXTys1MTiJcpd54ORMxelnOo5ZBs65GDI= X-Google-Smtp-Source: ABdhPJzGNwKNrEQ17Y5l9D/xnyFiHQT9k3uFaBO47Rq4mL6fXGpQGFl1uCPC8jhTiPD6MpVJqVJ+9WMd61dca/RDdOQ= X-Received: by 2002:a9d:ed2:0:b0:60a:de4f:bd93 with SMTP id 76-20020a9d0ed2000000b0060ade4fbd93mr1369750otj.40.1652960303323; Thu, 19 May 2022 04:38:23 -0700 (PDT) MIME-Version: 1.0 From: Zopolis0 Date: Thu, 19 May 2022 21:38:12 +1000 Message-ID: Subject: Patch structure and timing for re-adding gcj To: gcc-patches@gcc.gnu.org X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2022 11:38:26 -0000 Over the past few months I have been working on re-adding gcj to gcc ( https://github.com/Zopolis4/gcj/tree/mster). It is now at the point where all of the code in gcc/java and the related additions to other gcc files compiles successfully, although libjava still breaks. Given that I do not know how long it will be before it compiles successfully, nor the remaining issues preventing it from compiling it successfully, I was wondering if it would make sense to submit the gcc/java (and the related additions) code now, as to have it receive treewide changes rather than mysteriously breaking when I rebase and further slowing down development. This would also allow me to test files in libjava with the system gcc, among other things, as they make use of several types declared in gcc/java. Regardless of this, when all the code works, how should I submit it? My current plan is to have an initial commit re-adding the gcc/java and libjava directories in the exact state that they were removed, as so to have a clean history, and also adding the java-related code in other gcc files in a modern state. Then, a second commit modernising the code in gcc/java and libjava.