Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

C error only with -autofree flag. #19495

Closed
islonely opened this issue Oct 2, 2023 · 0 comments · Fixed by #19515
Closed

C error only with -autofree flag. #19495

islonely opened this issue Oct 2, 2023 · 0 comments · Fixed by #19515
Labels
Bug This tag is applied to issues which reports bugs. Build V build error on any OS/CPU architecture. Unit: cgen Bugs/feature requests, that are related to the default C generating backend. Unit: Memory Management Bugs/feature requests, that are related to the memory management of the compiler.

Comments

@islonely
Copy link
Contributor

islonely commented Oct 2, 2023

Describe the bug

A C error is generated from maybe_error()! only when -autofree flag is set.

Reproduction Steps

import os

fn maybe_error() !string {
	return 'string'
}

fn return_string_result() ! {
	os.write_file('./test.txt', maybe_error()!)!
}

fn main() {
	return_string_result() or {
		println(err.msg())
		exit(1)
	}
}

Expected Behavior

Expected code to write a file with string inside of it.

Current Behavior

==================
C:/Users/imado/AppData/Local/Temp/v_0/test.7251254077606544120.tmp.c:18212: warning: assignment from incompatible pointer type
C:/Users/imado/AppData/Local/Temp/v_0/test.7251254077606544120.tmp.c:18307: error: 'esult_string' undeclared
...
==================
(Use `v -cg` to print the entire error message)

builder error: 
==================
C error. This should never happen.

Possible Solution

No response

Additional Information/Context

No response

V version

V full version: V 0.4.2 ae5b4bb.c030c5e

Environment details (OS name and version, etc.)

V full version: V 0.4.2 ae5b4bb.c030c5e
OS: windows, Microsoft Windows 11 Pro v22621 64-bit
Processor: 16 cpus, 64bit, little endian, 

getwd: C:\Users\imado\Documents\GitHub\time_without
vexe: C:\Users\imado\v\v.exe
vexe mtime: 2023-09-30 16:48:31

vroot: OK, value: C:\Users\imado\v
VMODULES: OK, value: C:\Users\imado\.vmodules
VTMP: OK, value: C:\Users\imado\AppData\Local\Temp\v_0

Git version: git version 2.33.1.windows.1
Git vroot status: 0.4.2-3-gc030c5ef (14 commit(s) behind V master)
.git/config present: true

CC version: Error: 'cc' is not recognized as an internal or external command,
operable program or batch file.

thirdparty/tcc status: thirdparty-windows-amd64 e90c2620

Note

You can vote for this issue using the 👍 reaction. More votes increase the issue's priority for developers.

Take into account that only the 👍 reaction counts as a vote.
Only reactions to the issue itself will be counted as votes, not comments.

@islonely islonely added the Bug This tag is applied to issues which reports bugs. label Oct 2, 2023
@islonely islonely changed the title C error only with -autofree flag.` C error only with -autofree flag. Oct 3, 2023
@ArtemkaKun ArtemkaKun added Unit: Memory Management Bugs/feature requests, that are related to the memory management of the compiler. Unit: cgen Bugs/feature requests, that are related to the default C generating backend. Build V build error on any OS/CPU architecture. labels Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug This tag is applied to issues which reports bugs. Build V build error on any OS/CPU architecture. Unit: cgen Bugs/feature requests, that are related to the default C generating backend. Unit: Memory Management Bugs/feature requests, that are related to the memory management of the compiler.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants