On Sun, Apr 8, 2018 at 8:56 PM, Damian Rouson
wrote:
> On April 4, 2018 at 1:12:25 AM, Richard Biener
> (richard.guent...@gmail.com(mailto:richard.guent...@gmail.com)) wrote:
>
>> In that case user programs compiled with -fcoarray=lib are but gfortran
>> or libgfortran itself is not linked agains
On 04/08/2018 08:22 AM, Jeff Law wrote:
On 03/31/2018 12:27 PM, Richard W.M. Jones wrote:
I'd like to talk about what changes we (may) need to GCC in
Fedora to get it working on 64-bit RISC-V, and also (more
importantly) to ask your advice on things we don't fully
understand yet. However, I don
Hi everyone,
I goal is to discuss if we should use the compiler available in the build
machine (for example, in RHEL 6.5 it is GCC v4.4.7) or if we should use the
previous version of Cadence GCC (for example v4.8.3).
Currently, we use the lastest officially supported Cadence GCC version.
But w
On 9 April 2018 at 20:29, Rogerio de Souza Moraes wrote:
> Hi everyone,
>
> I goal is to discuss if we should use the compiler available in the build
> machine (for example, in RHEL 6.5 it is GCC v4.4.7) or if we should use the
> previous version of Cadence GCC (for example v4.8.3).
>
> Currently
On 04/09/2018 12:04 PM, Jim Wilson wrote:
> On 04/08/2018 08:22 AM, Jeff Law wrote:
>> On 03/31/2018 12:27 PM, Richard W.M. Jones wrote:
>>> I'd like to talk about what changes we (may) need to GCC in
>>> Fedora to get it working on 64-bit RISC-V, and also (more
>>> importantly) to ask your advice
On Mon, Apr 9, 2018 at 6:37 PM, Jeff Law wrote:
> On 04/09/2018 12:04 PM, Jim Wilson wrote:
>> On 04/08/2018 08:22 AM, Jeff Law wrote:
>>> On 03/31/2018 12:27 PM, Richard W.M. Jones wrote:
I'd like to talk about what changes we (may) need to GCC in
Fedora to get it working on 64-bit RISC
On 04/09/2018 04:47 PM, Stef O'Rear wrote:
> On Mon, Apr 9, 2018 at 6:37 PM, Jeff Law wrote:
>> On 04/09/2018 12:04 PM, Jim Wilson wrote:
>>> On 04/08/2018 08:22 AM, Jeff Law wrote:
On 03/31/2018 12:27 PM, Richard W.M. Jones wrote:
> I'd like to talk about what changes we (may) need to GC
Hi Jeff:
You can use -r option (e.g. ./qemu-riscv64 -r 4.15) or set QEMU_UNAME
environment variable to change the uname for qemu.
On Tue, Apr 10, 2018 at 6:50 AM, Jeff Law wrote:
> On 04/09/2018 04:47 PM, Stef O'Rear wrote:
>> On Mon, Apr 9, 2018 at 6:37 PM, Jeff Law wrote:
>>> On 04/09/2018 12
On Mon, Apr 09, 2018 at 04:37:30PM -0600, Jeff Law wrote:
> Are you guys using qemu user mode emulation for testing purposes? When
> I've set up a suitable riscv64 rootfs and try to do anything nontrivial
> in it with qemu user mode emulation it immediately complains that my
> kernel is too old --
