yy_parse completely fails on riscv64 architecture

[gyx47]

Description:

When deploying libsieve to parse files under riscv64 architecture, it is found that no matter what the input is, a syntax error will be returned.

Running ./example script1.sv messagea.mbox
Validating script...Error is SCRIPT PARSE:   Line is 8
  Message is syntax error
 not valid.
Executing script...
Error is SCRIPT PARSE:   Line is 15
  Message is syntax error
  no actions taken; keeping message.
Action is KEEP
Test failed for script1.sv with messagea.mbox

environment

• libsieve-2.3.1-6
• Platform: RISC-V 64
• log files:

My operating environment is an riscv64 environment virtual machine of the arch architecture of Windows WSL.

reproduce

The process is as follows:

1. Prepare the necessary environment
2. run ./configure --prefix=/usr
3. run(cd src/sv_parser && for i in ls -1 *.l | sed 's|.l||'; do flex --header-file=$i.h -o $i.c $i.l; done)
4. runmake
5. run./src/sv_test/example ./src/sv_test/script1.sv ./src/sv_test/messagea.mbox

debug

After experimentation, it is known that there is no problem from extracting the script file to storing buf. However, after yyparse of the libsieve_sieveparse function, a syntax error is always output. This is probably due to the memory and byte offset problems caused by the architecture. As a result, the subsequent libsieve_callback_do and cur_call.values ​​have problems, and the script finally returns NULL.

[gyx47]

I looked at the configure.log and the generated makefile. There was no difference except for the different compilers. There was no error, but the file parsing failed under yun'xriscv64, but was normal under X86.
Although the error reported was a syntax error, I checked the syntax specification file and found no problem. I found that even the simplest test failed, so it was not a simple riscv64 format problem. It was a problem in the lower-level assembly implementation.
The problem almost certainly lies in the syntax parsing of sieve.c in the current riscv64 environment. There may be low-level runtime problems related to the riscv64 architecture, such as memory alignment and pointer processing, which may cause the internal state of the parser to be corrupted and may cause YYABORT of stack clearing. Unfortunately, I spent a lot of time and found that I couldn't fix it.