Mercury Bugs - mercury | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000567 | mercury | Bug | public | 2023-11-07 13:00 | 2023-11-08 17:59 |
| Reporter | wangp | ||||
|---|---|---|---|---|---|
| Assigned To | zs | ||||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Summary | 0000567: regression due to merging consecutive switches | ||||
| Description | I have bisected a regression to commit 43dd12bd5b9608dcd150ea0c7bdc1e3f256f15d2 "Merge consecutive switches on the same variable." See the attached test case. This is incorrect: % mmc -O2 regression_merge_switches && ./regression_merge_switches header(field_name("Message-ID"), header_value("Tue, 7 Nov 2023 12:29:43 +1100")) header(field_name("Message-ID"), header_value("<20231107122943.GB219@example>")) The correct output is this: % mmc -O1 regression_merge_switches && ./regression_merge_switches header(field_name("Date"), header_value("Tue, 7 Nov 2023 12:29:43 +1100")) header(field_name("Message-ID"), header_value("<20231107122943.GB219@example>")) | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files |  regression_merge_switches.m (2,046) 2023-11-07 13:00https://bugs.mercurylang.org/file_download.php?file_id=324&type=bug | ||||
| Notes | |||||
|
|
|||||
|
|
||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
|---|---|---|---|---|---|
| 2023-11-07 13:00 | wangp | New Issue | |||
| 2023-11-07 13:00 | wangp | File Added: regression_merge_switches.m | |||
| 2023-11-07 23:50 | zs | Assigned To | => zs | ||
| 2023-11-07 23:50 | zs | Status | new => assigned | ||
| 2023-11-08 17:59 | zs | Status | assigned => resolved | ||
| 2023-11-08 17:59 | zs | Resolution | open => fixed | ||
| 2023-11-08 17:59 | zs | Note Added: 0001226 | |||