[Bug binutils/26206] Add pei-aarch64 support for native EFI support

2021-10-15 Thread steve-sourceware at einval dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 --- Comment #17 from Steve McIntyre --- (In reply to Tamar Christina from comment #16) > hmmm It looks like I'm dropped to a QEMU shell. > > (qemu) info status > VM status: running > > which says running, perhaps I can't do this over SSH and

[Bug binutils/26206] Add pei-aarch64 support for native EFI support

2021-10-15 Thread tnfchris at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 --- Comment #16 from Tamar Christina --- hmmm It looks like I'm dropped to a QEMU shell. (qemu) info status VM status: running which says running, perhaps I can't do this over SSH and a window has popped up on the desktop? If so I'll check i

[Bug binutils/26206] Add pei-aarch64 support for native EFI support

2021-10-15 Thread steve-sourceware at einval dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 --- Comment #15 from Steve McIntyre --- Hmmm, OK. That UEFI image (when padded up to 64MiB) starts here and will let me start an OS or go into the shell OK. Are you getting any errors?(In reply to Tamar Christina from comment #14) > (In reply

[Bug binutils/26206] Add pei-aarch64 support for native EFI support

2021-10-15 Thread tnfchris at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 --- Comment #14 from Tamar Christina --- (In reply to Steve McIntyre from comment #13) > Hmmm, OK. > > That UEFI image (when padded up to 64MiB) starts here and will let me start > an OS or go into the shell OK. Are you getting any errors? N

[Bug binutils/26206] Add pei-aarch64 support for native EFI support

2021-10-15 Thread steve-sourceware at einval dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 --- Comment #13 from Steve McIntyre --- Hmmm, OK. That UEFI image (when padded up to 64MiB) starts here and will let me start an OS or go into the shell OK. Are you getting any errors? -- You are receiving this mail because: You are on the

[Bug binutils/26206] Add pei-aarch64 support for native EFI support

2021-10-15 Thread tnfchris at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 --- Comment #12 from Tamar Christina --- (In reply to Steve McIntyre from comment #11) > Hi! > > Do you have an existing UEFI image (e.g. edk2 AAVMF) to use for testing with? I have been attempting to use QEMU_EFI.fd from http://snapshots.l

[Bug binutils/26206] Add pei-aarch64 support for native EFI support

2021-10-15 Thread steve-sourceware at einval dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 --- Comment #11 from Steve McIntyre --- Hi! Do you have an existing UEFI image (e.g. edk2 AAVMF) to use for testing with? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug binutils/26206] Add pei-aarch64 support for native EFI support

2021-10-15 Thread tnfchris at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 --- Comment #10 from Tamar Christina --- Does anyone happen to know of an easy(ish) way I can test this? I've downloaded and modified https://sourceforge.net/projects/gnu-efi/ to remove the hacks and fixed up the linker script. I can now pro

[Bug gold/28417] std::string no longer allows accepting nullptr_t since it is undefined behavior after yesterday's change on libstdc++.

2021-10-15 Thread jwakely.gcc at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28417 --- Comment #10 from Jonathan Wakely --- Alan was replying to comment 6 where I said the default constructor could just be removed. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gold/28417] std::string no longer allows accepting nullptr_t since it is undefined behavior after yesterday's change on libstdc++.

2021-10-15 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28417 --- Comment #9 from cqwrteur --- (In reply to Alan Modra from comment #7) > gold continues to be built with older compilers such as gcc-4.8 which > default to c++98. So beware relying on c++11. (I've been tripped up using > c++11 features in