Re: libgo patch committed: Update to Go1.14beta1

On Sat, Feb 1, 2020 at 2:38 PM Andreas Schwab wrote: > ../../../libgo/go/syscall/syscall_linux_riscv64.go:7:14: error: imported > and not used: unsafe > 7 | import "unsafe" > | ^ I see the same issue in Fedora/RISCV, the last two builds of GCC 10 failed due to it. Btw, 1

Re: [PATCH] RISC-V: Add minimal support for 7 new unprivileged extensions

On Thu, Feb 1, 2024 at 10:43 AM Kito Cheng wrote: > Could you add some document for doc/invoke.texi, I just added a list > for listing all supported extensions before[1]. > > [1] > https://github.com/gcc-mirror/gcc/commit/19260a04ba6f75b1fae52afab50dcb43d44eb259 Offtopic, but looking at the fil

Re: [PATCH, PR 57748] Set mode of structures with zero sized arrays to be BLK

ping^2 david On Aug 12, 2013, at 2:31 PM, David Abdurachmanov wrote: > Hi, > > Ping. Any news of the following patch being included into the trunk? > > Thanks, > david > > On Aug 2, 2013, at 1:45 PM, Martin Jambor wrote: > >> Hi, >> >> while co

Re: [PATCH] Backport of RISC-V support for libffi

I am using the same changes in Fedora RISC-V with GCC 8.0.1-0.19 (libffi patch + s/FFI_ALIGN/ALIGN/ + regen). Note that libffi port is missing go closures support. Small things like hello world work fine, but utilities like "go" will complain with run- time error: fatal error: libgo built without

Re: [PATCH] Backport of RISC-V support for libffi

On Tue, 2018-03-20 at 12:09 +0100, Andreas Schwab wrote: > On Mär 20 2018, David Abdurachmanov wrote: > > > What is the current situation/resolution regarding GOARCH? GCC use > > RISCV64, but golang port uses RISCV. It would be nice to have a > > resolution before GCC

Re: [PING ^ 3] [RFC PATCH, AARCH64] Add support for -mlong-calls option

Ping. This was posted in Stage 1, thus still should be valid for Stage 3. First we hit a issue with OpenLoops package were we generated big functions bodies (1-2MB) [1]. This caused the GNU assembler not to be happy as it generated PC-relative offsets to literal pool above 1MB. The authors of pa

[PATCH] D support for RISC-V

: David Abdurachmanov --- libphobos/configure.tgt | 2 + libphobos/libdruntime/core/atomic.d | 6 +- .../libdruntime/rt/sections_elf_shared.d | 14 - .../allocator/building_blocks/region.d| 3 +- libphobos/src/std/math.d | 59

Re: [PATCH] D support for RISC-V

On Tue, Apr 9, 2019 at 12:22 PM Andreas Schwab wrote: > > On Apr 09 2019, David Abdurachmanov wrote: > > > diff --git > > a/libphobos/src/std/experimental/allocator/building_blocks/region.d > > b/libphobos/src/std/experimental/allocator/building_blocks/reg

Re: [PATCH] Fix PR c++/21802 (two-stage name lookup fails for operators

> On 15 Jan 2016, at 05:10, Patrick Palka wrote: > > On Thu, 14 Jan 2016, Ryan Burn wrote: > >> Also caused https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69091 > > Thanks for the heads up, I was not aware I had caused this regression. While looking at last few failures with GCC 6.0.0 in our so

Re: libsanitizer merge from upstream r221802

Hi, I believe this is breaking bootstrap on aarch64-linux-gnu with kernels <=3.15, 3.16 and above are fine. __kernel_old_{gid,uid}_t were changed in 3.16 from unsigned int to unsigned short. <=3.15 kernel will trigger static asserts in libsanitizer while compiling GCC. I created PR: https://gcc.

Re: libsanitizer merge from upstream r221802

Hi, I believe this is breaking bootstrap on aarch64-linux-gnu with kernels <=3.15, 3.16 and above are fine. __kernel_old_{gid,uid}_t were changed in 3.16 from unsigned int to unsigned short. <=3.15 kernel will trigger static asserts in libsanitizer while compiling GCC. I created PR: https://gcc.

Re: libsanitizer merge from upstream r221802

On Dec 29, 2014, at 7:46 PM, Jakub Jelinek wrote: > On Mon, Dec 29, 2014 at 07:36:42PM +0100, David Abdurachmanov wrote: >> I believe this is breaking bootstrap on aarch64-linux-gnu with kernels >> <=3.15, >> 3.16 and above are fine. >> >> __kernel_old_{

Re: libsanitizer merge from upstream r221802

On Dec 30, 2014, at 11:48 PM, Andrew Pinski wrote: >> If we have 64-bit kernel and 64-bit application is executed sys_getresuid is >> used for getresuid syscall, otherwise if 32-bit application is executed -- >> sys_getresuid16 is used. Thus 64-bit application will never call >> sys_getresuid16 im

Re: [PATCH, PR 57748] Set mode of structures with zero sized arrays to be BLK

Hi, Ping. Any news of the following patch being included into the trunk? Thanks, david On Aug 2, 2013, at 1:45 PM, Martin Jambor wrote: > Hi, > > while compute_record_mode in stor-layout.c makes sure it assigns BLK > mode to structs with flexible arrays, it has no such provisions for > zero le

Re: [PATCH, PR 57748] Set mode of structures with zero sized arrays to be BLK

Hi, Ping. Any news of the following patch being included into the trunk? Thanks, david On Aug 2, 2013, at 1:45 PM, Martin Jambor wrote: > Hi, > > while compute_record_mode in stor-layout.c makes sure it assigns BLK > mode to structs with flexible arrays, it has no such provisions for > zero le

Re: [PATCH v4] RISC-V: Add support for inlining subword atomic operations

On Fri, Sep 2, 2022 at 1:09 PM Kito Cheng via Gcc-patches < gcc-patches@gcc.gnu.org> wrote: > LGTM with minor comments, it's time to move forward, thanks Patrick and > Palmer. > Ping. Any plans to finally land this one for GCC 13? The hope is that this patch would make life significantly easier