Sanitizer CHECK failed: sanitizer_allocator_primary64.h:133

[Deepthi H via Gcc]

Hi,

I am facing the issue on enabling sanitizers for gcc on aarch64 linux.
The issue was observed with the following command :-
"aarch64-poky-linux-gcc -O1 -fsanitize=address -fno-omit-frame-pointer -o
test test.c"

*AddressSanitizer: CHECK failed: sanitizer_allocator_primary64.h:131
"((kSpaceBeg)) == ((address_range.Init(TotalSpaceSize,
PrimaryAllocatorName, kSpaceBeg)))" (0x6000, 0xfff4)
(tid=389)*

I found a patch that fixes the sanitizer issue for arm64  on llvm :-
⚙D60243 [LSan][AArch64] Speed-up leak and address sanitizers on AArch64 for
48-bit VMA (llvm.org) 

I analyzed and tried to port the patch that fixes the issue for llvm. After
backporting the LLVM patches to the GCC sources, I encountered several
build errors, particularly related to the AddressSanitizer (ASan) and
LeakSanitizer (LSan) libraries. I have fixed lsan and asan issues. However
sanitizer_common is completely different in gcc than llvm.
Can you please help me fix this issue on gcc sources or is than any other
way to fix this issue.

Thanks in advance,
Deepthi

Sourceware Open Office, Friday February 9, 18:00 UTC

[Mark Wielaard]

Hi Sourceware projects hackers,

2024 started strong with various Sourceware core toolchain and
developer tool projects presenting at Fosdem. If you missed the in
person meetings, most talks have video recordings:

https://fosdem.org/2024/schedule/track/debuggers-and-analysis/
https://fosdem.org/2024/schedule/track/gcc/

Various Sourceware volunteers, overseers and project leadership
committee members also met informally with FSF/GNU and SFC admins to
coordinate cross free software infrastructure administration matters.

If you want to chat about any of this, please join us this Friday,
February 9, in #overseers on irc.libera.chat from 18:00 till 19:00 UTC.

Want to update your gitweb URLs to cgit? Need help adjusting
infrastructure tools for more efficient contributor workflows? Setting
up a git backed documentation/website? Have ideas or opinions on secure
supply chain and code signing? Want to take advantage of the new risc-v
VisionFive-2 boards that StarFive donated for buildbot CI runs?

In general for any questions or ideas about any Sourceware service
and/or integration of cgit, bugzilla, mailinglists, snapshots, mirrors,
archiving, gitsigur, public-inbox, b4, patchwork, bbb, buildbot, etc.
we are here to help.

For this meeting we will also have a BBB meeting room:
https://bbb.sfconservancy.org/b/mar-aom-dmo-fko
(But the real discussion will be in the irc channel)

If you want to run your own meetings for any Sourceware project you can
create your own account at https://bbb.sfconservancy.org/b/signup which
we can then activate for you. Note: Anyone is able to join a meeting,
accounts are only required to create new meetings.

Of course you are welcome to drop into the #overseers channel at any
time and we can also be reached through email and bugzilla:
https://sourceware.org/mission.html#organization

Thanks to the Conservancy we now also have a donation page:
  https://sourceware.org/donate.html
to fund accelerating tasks the community feels most useful. More
details about our relationship with the Conservancy here:
https://sfconservancy.org/blog/2023/nov/27/sourceware-thanks-conservancy/

If you aren't already and want to keep up to date on Sourceware
infrastructure services then please also subscribe to the overseers
mailinglist. https://sourceware.org/mailman/listinfo/overseers

We are also on the fediverse these days:
https://fosstodon.org/@sourceware

The Sourceware Project Leadership Committee also meets once a month to
discuss all community input. The committee will set priorities and
decide how to spend any funds, negotiate with hardware and service
partners, create budgets together with the Conservancy, or decides when
a new fundraising campaign is needed. The current committee includes
Frank Ch. Eigler, Christopher Faylor, Ian Kelling, Ian Lance Taylor,
Tom Tromey, Jon Turney, Mark J. Wielaard and Elena Zannoni.

gcc-11-20240208 is now available

[GCC Administrator via Gcc]

Snapshot gcc-11-20240208 is now available on
  https://gcc.gnu.org/pub/gcc/snapshots/11-20240208/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch 
releases/gcc-11 revision 03c43045300d0ed9997c4de4c011765f6a7fde7e

You'll find:

 gcc-11-20240208.tar.xz   Complete GCC

  SHA256=93d2ae16ef10ad19fd364199f256c49cef60ae225509bbfa52bb2cd605d91266
  SHA1=06b240ff39db741d3ad813324455209f6bc411bd

Diffs from 11-20240201 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-11
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.