public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/111544] New: [14 regression] assignment of read-only location after r14-4111-g6e92a6a2a72d3b
Date: Fri, 22 Sep 2023 18:59:03 +0000 [thread overview]
Message-ID: <bug-111544-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111544
Bug ID: 111544
Summary: [14 regression] assignment of read-only location after
r14-4111-g6e92a6a2a72d3b
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
Starting with r14-4111-g6e92a6a2a72d3b I am seeing a whole bunch of errors when
compiling some test code like this:
/home/seurer/gcc/git/install/gcc-test//bin/g++ -c -o WFXMLScanner.o -DSPEC_CPU
-DNDEBUG -DAPP_NO_THREADS -DXALAN_INMEM_MSG_LOADER -I. -Ixercesc -Ixercesc/dom
-Ixercesc/dom/impl -Ixercesc/sax -Ixercesc/util/MsgLoaders/InMemory
-Ixercesc/util/Transcoders/Iconv -Ixalanc/include -DPROJ_XMLPARSER
-DPROJ_XMLUTIL -DPROJ_PARSERS -DPROJ_SAX4C -DPROJ_SAX2 -DPROJ_DOM
-DPROJ_VALIDATORS -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER
-m64 -O3 -mcpu=power8 -fpeel-loops -funroll-loops -ffast-math -mpopcntd
-mrecip=all -DSPEC_CPU_LP64 -DSPEC_CPU_LINUX WFXMLScanner.cpp
In file included from ./xercesc/util/NameIdPool.hpp:338,
from ./xercesc/internal/XMLScanner.hpp:311,
from ./xercesc/internal/WFXMLScanner.hpp:93,
from WFXMLScanner.cpp:65:
./xercesc/util/NameIdPool.c: In member function
'xercesc_2_5::NameIdPoolEnumerator<TElem>&
xercesc_2_5::NameIdPoolEnumerator<TElem>::operator=(const
xercesc_2_5::NameIdPoolEnumerator<TElem>&)':
./xercesc/util/NameIdPool.c:416:20: error: assignment of read-only location
'((xercesc_2_5::NameIdPoolEnumerator<TElem>*)this)->xercesc_2_5::NameIdPoolEnumerator<TElem>::fMemoryManager'
416 | fMemoryManager = toAssign.fMemoryManager;
| ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~
This is old, old code (one of the tests in spec 2006) and appears to run just
fine. Is there actually something wrong in the code or is the error message in
error?
commit 6e92a6a2a72d3b7a5e1b29042d8a6a43fe1085aa (HEAD)
Author: Patrick Palka <ppalka@redhat.com>
Date: Mon Sep 18 14:47:52 2023 -0400
c++: non-dependent assignment checking [PR63198, PR18474]
next reply other threads:[~2023-09-22 18:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 18:59 seurer at gcc dot gnu.org [this message]
2023-09-22 19:09 ` [Bug other/111544] " sjames at gcc dot gnu.org
2023-09-22 19:51 ` seurer at gcc dot gnu.org
2023-09-22 20:04 ` [Bug c++/111544] " pinskia at gcc dot gnu.org
2023-09-22 20:11 ` sjames at gcc dot gnu.org
2023-09-22 20:16 ` sjames at gcc dot gnu.org
2023-09-22 20:23 ` pinskia at gcc dot gnu.org
2023-09-22 20:32 ` pinskia at gcc dot gnu.org
2023-09-22 20:34 ` sjames at gcc dot gnu.org
2023-09-22 20:47 ` sjames at gcc dot gnu.org
2023-09-22 21:00 ` pinskia at gcc dot gnu.org
2023-09-22 21:17 ` seurer at gcc dot gnu.org
2023-09-24 9:41 ` redi at gcc dot gnu.org
2023-09-24 9:41 ` redi at gcc dot gnu.org
2023-10-10 17:49 ` seurer at gcc dot gnu.org
2024-01-17 17:53 ` sjames at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-111544-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).