Re: [GHC] #7406: -ddump-ds does not turn on -fforce-recomp

2012-11-14 Thread GHC
#7406: -ddump-ds does not turn on -fforce-recomp +--- Reporter: goldfire | Owner: igloo Type: bug | Status: infoneeded Priority: normal

Re: [GHC] #7406: -ddump-ds does not turn on -fforce-recomp

2012-11-14 Thread GHC
#7406: -ddump-ds does not turn on -fforce-recomp +--- Reporter: goldfire | Owner: igloo Type: bug | Status: new Priority: normal

Re: [GHC] #7406: -ddump-ds does not turn on -fforce-recomp

2012-11-14 Thread GHC
#7406: -ddump-ds does not turn on -fforce-recomp +--- Reporter: goldfire | Owner: igloo Type: bug | Status: new Priority: normal

Re: [GHC] #7406: -ddump-ds does not turn on -fforce-recomp

2012-11-13 Thread GHC
#7406: -ddump-ds does not turn on -fforce-recomp +--- Reporter: goldfire | Owner: igloo Type: bug | Status: new Priority: normal

Re: [GHC] #7406: -ddump-ds does not turn on -fforce-recomp

2012-11-13 Thread GHC
#7406: -ddump-ds does not turn on -fforce-recomp +--- Reporter: goldfire | Owner: igloo Type: bug | Status: infoneeded Priority: normal

Re: [GHC] #7406: -ddump-ds does not turn on -fforce-recomp

2012-11-13 Thread GHC
#7406: -ddump-ds does not turn on -fforce-recomp +--- Reporter: goldfire | Owner: igloo Type: bug | Status: infoneeded Priority: normal

[GHC] #7406: -ddump-ds does not turn on -fforce-recomp

2012-11-12 Thread GHC
#7406: -ddump-ds does not turn on -fforce-recomp -+-- Reporter: goldfire | Owner: Type: bug | Status: new Priority: normal| Component

Re: [GHC] #6105: GHCi does no respect -fforce-recomp

2012-06-05 Thread GHC
#6105: GHCi does no respect -fforce-recomp ---+ Reporter: SimonHengel | Owner: simonmar Type: bug | Status: closed Priority: high | Milestone: 7.4.2

Re: [GHC] #6105: GHCi does no respect -fforce-recomp

2012-05-22 Thread GHC
#6105: GHCi does no respect -fforce-recomp ---+ Reporter: SimonHengel | Owner: simonmar Type: bug | Status: new Priority: high| Milestone: 7.4.2

Re: [GHC] #6105: GHCi does no respect -fforce-recomp

2012-05-22 Thread GHC
#6105: GHCi does no respect -fforce-recomp ---+ Reporter: SimonHengel | Owner: simonmar Type: bug | Status: merge Priority: high| Milestone: 7.4.2

Re: [GHC] #6105: GHCi does no respect -fforce-recomp

2012-05-21 Thread GHC
#6105: GHCi does no respect -fforce-recomp ---+ Reporter: SimonHengel | Owner: simonmar Type: bug | Status: new Priority: high| Milestone: 7.4.2

[GHC] #6105: GHCi does no respect -fforce-recomp

2012-05-17 Thread GHC
#6105: GHCi does no respect -fforce-recomp --+- Reporter: SimonHengel | Owner: Type: bug | Status: new Priority: normal| Component: GHCi

-recomp

1997-10-03 Thread Alex Ferguson
Has anyone noticed anything flakey about the 2.07 recompilation system? I've noticed several unnecessary-looking version changes and the like since switching over. Any chance it might be confused by hi's left around from version version (2.05), or some such? Sorry to be so vague, but I fear

Re: -recomp

1997-10-03 Thread Sigbjorn Finne
Alex Ferguson writes: BTW, did there use to be/is there still an option to tell -recomp to be explicit about why it had to do a recompilation? I found -hi-diffs-with-usages, which was of some help, but I thought there was a more directly useful one too, but I couldn't lay my hands

Re: -recomp

1997-10-03 Thread Alex Ferguson
Further to my previous message: What it looks like is that I have a cycle of module deps, and whenever any of them are changed, -recomp gets very confused and recompiles them all. This seems to be because each of them becomes a new version because its usages because its predecessor

Re: Error in 2.01 -recomp

1997-02-12 Thread Simon L Peyton Jones
| If a new symbol is added, (apparently) no test is made to see if this | causes a clash with existing symbols in higher-level modules. | | Also, moving a function from one module to another sometimes confuses | the recomp system, when it's looking for it in the "old" place: