[Bug c++/105921] New: internal compiler error: in cp_parser_template_id, at cp/parser.cc:18362

2022-06-10 Thread orbisvicis+gcc at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105921

Bug ID: 105921
   Summary: internal compiler error: in cp_parser_template_id, at
cp/parser.cc:18362
   Product: gcc
   Version: 12.1.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
  Assignee: unassigned at gcc dot gnu.org
  Reporter: orbisvicis+gcc at gmail dot com
  Target Milestone: ---

Created attachment 53117
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53117&action=edit
bug.cxx.i

[Bug c++/105921] internal compiler error: in cp_parser_template_id, at cp/parser.cc:18362

2022-06-10 Thread orbisvicis+gcc at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105921

--- Comment #1 from Yclept Nemo  ---
AFAICT, the attachment includes everything needed in a bug report. Inlining the
code here for convenience:

#include 

template 
auto a = (struct A {
template 
using Temp = T1;

template 
auto get(std::index_sequence){
return (int (*)( Temp... ))nullptr;
}
}){}.get(std::make_index_sequence{});

int main () {
a;
}

[Bug fortran/113671] New: Passing allocatable character(:) slices with negative stride: invalid memory access / segfault

2024-01-30 Thread orbisvicis+gcc at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113671

Bug ID: 113671
   Summary: Passing allocatable character(:) slices with negative
stride: invalid memory access / segfault
   Product: gcc
   Version: 13.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
  Assignee: unassigned at gcc dot gnu.org
  Reporter: orbisvicis+gcc at gmail dot com
  Target Milestone: ---

Created attachment 57262
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57262&action=edit
Various conditions to explore the invalid memory access

When passing an allocatable character(:) slice with negative stride, gfortran
either segfaults or accesses invalid memory.

* GNU Fortran (GCC) 11.4.0 on Cygwin 3.4.7-1.x86_64 segfaults (invalid memory
access)
* x86_64 GFortran 13.2|trunk on godbolt.org accesses invalid memory

Actual output:

```
testing:1   3   5
   one  

   !
```

Expected output:

```
testing:1   3   5
   three
   two  
   one
```