Original bug ID: 7738 Reporter:@rixed Assigned to:@gasche Status: resolved (set by @gasche on 2018-02-21T10:45:02Z) Resolution: fixed Priority: normal Severity: minor Version: 4.06.1 Fixed in version: 4.07.0+dev/beta2/rc1/rc2 Category: compiler driver
Bug description
When using the compiler-libs in a program and trying to compile several source codes I noticed some options to gcc accumulated from one compilation to the next, despite I've tried to cleaned as many global variables as I could, including via Asmlink.reset().
Problem seems to be that the aforementioned reset function does not clean lib_ccobjs or lib_ccopts.
A quick test suggest that cleaning those does fix my issue without introducing any bug I could notice.
The text was updated successfully, but these errors were encountered:
These variables are reset by Bytelibrarian.reset and Bytelink.reset, so indeed it seems correct to reset them in asmcomp/ modules that set them. Would you care to submit a Pull Request?
Original bug ID: 7738
Reporter: @rixed
Assigned to: @gasche
Status: resolved (set by @gasche on 2018-02-21T10:45:02Z)
Resolution: fixed
Priority: normal
Severity: minor
Version: 4.06.1
Fixed in version: 4.07.0+dev/beta2/rc1/rc2
Category: compiler driver
Bug description
When using the compiler-libs in a program and trying to compile several source codes I noticed some options to gcc accumulated from one compilation to the next, despite I've tried to cleaned as many global variables as I could, including via Asmlink.reset().
Problem seems to be that the aforementioned reset function does not clean lib_ccobjs or lib_ccopts.
A quick test suggest that cleaning those does fix my issue without introducing any bug I could notice.
The text was updated successfully, but these errors were encountered: