https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110399
--- Comment #3 from Chan Lewis ---
(In reply to Andrew Pinski from comment #2)
> Dup of bug 13421.
>
> *** This bug has been marked as a duplicate of bug 13421 ***
I see. I wonder why gcc consider pointer signed and need to abort in this
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: baiwfg2 at gmail dot com
Target Milestone: ---
The demo code is :
```c
#include
#include
#include
#include
int main() {
{
char *p = (char *)0x8001;
char *q
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91636
--- Comment #2 from Chan Lewis ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to Chan Lewis from comment #0)
> > My gcc 7.3.1 version info is:
> >
> > [root@VM_11_190_centos /data1/ethencao]# gcc -v
> > Using built-in specs.
> >
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: baiwfg2 at gmail dot com
Target Milestone: ---
Hi. I'm benchmarking const std::string optimization with different gcc version
and find that gcc 7.3.1 is not working well. Here's my benchmark code (I also
put
