| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0000092 | mercury | Bug | public | 2009-03-09 23:43 | 2025-07-10 00:09 | ||||
| Reporter | juliensf | ||||||||
| Assigned To | zs | ||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0000092: generated C code contains a block that defines a variable that shadows a headvar in hlc.gc | ||||||||
| Description | Compiling the C code generated for the attached module in the hlc.gc grade results in: shadowed_headvar.m: In function 'shadowed_headvar__type_defined_in_runtime_1_p_0': shadowed_headvar.m:64: warning: declaration of 'shadowed_headvar__HeadVar__1_1' shadows a parameter shadowed_headvar.m:38: warning: shadowed declaration is here | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
zs (developer) 2025-07-10 00:09 |
I think this bug was fixed, possibly unintentionally, soon after it was filed. In an email to m-rev on 2017 Apr 24, juliensf wrote about this bug: > IIRC I couldn't reproduce it with the rotd > from a few weeks after I found it. We certainly haven't been able to reproduce it since, and the current setup for deciding the names of the C variables representing Mercury variables *should* rule out any possibility of the reported shadowing. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-03-09 23:43 | juliensf | New Issue | |
| 2009-03-09 23:43 | juliensf | File Added: shadowed_headvar.m | |
| 2025-07-10 00:09 | zs | Assigned To | => zs |
| 2025-07-10 00:09 | zs | Status | new => closed |
| 2025-07-10 00:09 | zs | Resolution | open => fixed |
| 2025-07-10 00:09 | zs | Note Added: 0001234 | |
| Issue History |