New Issue: Compiler aborts on "this argument has unknown type"

aconsroe-hpe1 · February 18, 2022, 8:50pm

19280, "aconsroe-hpe", "Compiler aborts on "this argument has unknown type"", "2022-02-18T20:49:03Z"

Compiler aborts on "this argument has unknown type"

opened 08:49PM - 18 Feb 22 UTC

type: Bug issues week

When modifying a program, I had switched something to the effect of renaming `re…cord R` to `record _R` without changing the init methods. This currently aborts in the normalize pass: ```chapel proc R.init() {} ``` ``` chpl test/segfault.chpl ``` ``` ../chapel2/test/segfault.chpl:6: internal error: PAS-NOR-IZE-4531 chpl version 1.26.0 pre-release (2005de5b22) ``` ``` chpl --devel test/segfault.chpl ``` ``` test/segfault.chpl:6: internal error: 'this' argument has unknown type [passes/normalize.cpp:4533] ``` Today, that is: https://github.com/chapel-lang/chapel/blob/275f4fe65997bca8cbdba6079a37ccc7157f5676/compiler/passes/normalize.cpp#L4518-L4538 Reproduced on 1.25.1 and main. In this case, the `--devel` error message might be suitable to show the user because even though they both contain the file and line number, the `--devel` gives more info. Or maybe its best handled with a check earlier in the pipeline.

When modifying a program, I had switched something to the effect of renaming record R to record _R without changing the init methods. This currently aborts in the normalize pass:

proc R.init() {}

chpl test/segfault.chpl

../chapel2/test/segfault.chpl:6: internal error: PAS-NOR-IZE-4531 chpl version 1.26.0 pre-release (2005de5b22)

chpl --devel test/segfault.chpl

test/segfault.chpl:6: internal error: 'this' argument has unknown type [passes/normalize.cpp:4533]

Today, that is:

github.com

chapel-lang/chapel/blob/275f4fe65997bca8cbdba6079a37ccc7157f5676/compiler/passes/normalize.cpp#L4518-L4538

      
        
            static void updateInitMethod(FnSymbol* fn) {
              Type* thisType = fn->_this->type;
            
            
  if (isAggregateType(thisType) == true) {
            
            
    if (fn->name == astrInitEquals) {
                  if (isClass(thisType))
                    USR_FATAL_CONT(fn, "init= may not be defined on class types");
                  if (thisType->symbol->hasFlag(FLAG_EXTERN))
                    USR_FATAL_CONT(fn, "init= may not currently be defined on extern types");
                }
            
            
    preNormalizeInitMethod(fn);
            
            
  } else if (thisType == dtUnknown) {
                INT_FATAL(fn, "'this' argument has unknown type");
            
            
  } else {
                USR_FATAL_CONT(fn, "initializers may currently only be defined on class, record, or union types");
              }
            }

Reproduced on 1.25.1 and main.

In this case, the --devel error message might be suitable to show the user because even though they both contain the file and line number, the --devel gives more info. Or maybe its best handled with a check earlier in the pipeline.

Topic		Replies	Views
User-defined non-copy record initializer on other type breaks resolution of compiler's default copy-initializer Users	4	178	February 27, 2023
New chapel questions for Jun 28 - Stack Exchange Stack Overflow	0	198	June 28, 2022
Announcing Chapel 1.28.0! Announcements	0	374	September 16, 2022

New Issue: Compiler aborts on "this argument has unknown type"

Related Topics