| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0000393 | mercury | Bug | public | 2015-09-15 10:40 | 2015-09-18 06:57 | ||||
| Reporter | wangp | ||||||||
| Assigned To | zs | ||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | resolved | Resolution | fixed | ||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0000393: #line directives in .mh cause unnecessary recompilations | ||||||||
| Description | This is a source of mysterious recompilations that I was experiencing in debug grades. I had a mutable declaration near the *end* of a file: :- mutable(debug_num, int, 0, ground, [untrailed, attach_to_io_state]). resulting in a #line directive in the .mh file: #ifndef WRITEPDF__RASTER_DECL_GUARD #define WRITEPDF__RASTER_DECL_GUARD #line 1400 "../writepdf/raster.m" #ifdef MR_HIGHLEVEL_CODE extern MR_Integer writepdf__raster__mutable_variable_debug_num; #else extern MR_Word writepdf__raster__mutable_variable_debug_num; #endif #ifdef MR_THREAD_SAFE extern MercuryLock writepdf__raster__mutable_variable_debug_num_lock; #endif Adding or removing blank lines would be enough to triggering recompilation of seemingly unrelated .c files. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
zs (developer) 2015-09-18 06:57 |
Fixed 18 sep 2015 by commit 410c75c81f47d0a1f5620f1f41f4e7afe87c665d. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-09-15 10:40 | wangp | New Issue | |
| 2015-09-17 16:19 | zs | Assigned To | => zs |
| 2015-09-17 16:19 | zs | Status | new => assigned |
| 2015-09-18 06:57 | zs | Note Added: 0000848 | |
| 2015-09-18 06:57 | zs | Status | assigned => resolved |
| 2015-09-18 06:57 | zs | Resolution | open => fixed |
| Issue History |