[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1008891: RFS: gcc-sh-elf/3 -- GNU C compiler for embedded SuperH devices



Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: debian-superh@lists.debian.org
X-Debbugs-CC: pkg-electronics-devel@alioth-lists.debian.net

Dear mentors and other interested parties,

I am looking for a sponsor for my package "gcc-sh-elf":

 * Package name    : gcc-sh-elf
   Version         : 3
 * License         : GPL-3+
 * Vcs             :
https://salsa.debian.org/electronics-team/toolchains/gcc-sh-elf
   Section         : devel

The source builds the following binary packages:

  gcc-sh-elf - GNU C compiler for embedded SuperH devices
  libnewlib-sh-elf-dev - small ISO C standard library for embedded
SuperH devices

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/gcc-sh-elf/

Alternatively, you can download the package with 'dget' using this
command:

  dget -x
https://mentors.debian.net/debian/pool/main/g/gcc-sh-elf/gcc-sh-elf_3.dsc

Changes since the last upload:

 gcc-sh-elf (3) experimental; urgency=medium
 .
   * Switch to GCC 12.
   * Improve reproducibility by using tools in non-usrmerge locations
     with thanks to Vagrant Cascadian for the patch (Closes: #1003500)
   * Switch non-portable usage of echo to printf (Closes: #1003501)
     Thanks again to Vagrant.

Thanks to my running the GCC testsuite, which is uncommon for a cross-
compiler package, I've discovered a serious regression in GCC:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105069
This has not been fixed yet, and hence is why this upload is going to
experimental. When this gets fixed, I will make an additional
autopkgtest for it and tighten the gcc-12-source build-dep so it passes.

The goals of this upload are
 * to allow checking that carl9170fw builds with both GCC 11 and 12 by
reviewers when carl9170fw is ready
 * to see if the package is fully reproducible now, and
 * to catch any FTBFS issues that may arise with new GCC 12 uploads

Before uploading to unstable, I would also like to take additional time
to check for testsuite regressions, which of course anyone is welcome to
help with. Knowledge of GCC internals or its test suite is not needed,
as I've been able to do without.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: