March 2014 - ghc-tickets

Re: [GHC] #2110: Rules to eliminate casted id's
by GHC 13 Mar '14

13 Mar '14

#2110: Rules to eliminate casted id's -------------------------------------------------+------------------------- Reporter: igloo | Owner: Type: feature request | Status: Priority: lowest | closed Component: Compiler | Milestone: Resolution: fixed | 7.10.1 Operating System: Unknown/Multiple | Version: 6.8.2 Type of failure: None/Unknown | Keywords: Test Case: | Architecture: tests/simplCore/should_run/T2110 | Unknown/Multiple Blocking: | Difficulty: | Unknown | Blocked By: | Related Tickets: #8767 -------------------------------------------------+------------------------- Changes (by thoughtpolice): * testcase: => tests/simplCore/should_run/T2110 -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/2110#comment:49> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

[GHC] #8867: newArray# fails to initialize card table correctly
by GHC 13 Mar '14

13 Mar '14

#8867: newArray# fails to initialize card table correctly ------------------------------------+------------------------------------- Reporter: tibbe | Owner: simonmar Type: bug | Status: new Priority: normal | Milestone: Component: Runtime System | Version: 7.6.3 Keywords: | Operating System: Unknown/Multiple Architecture: Unknown/Multiple | Type of failure: None/Unknown Difficulty: Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | ------------------------------------+------------------------------------- `newArray#` doesn't initialize the card table correctly. It writes the init value to the card table instead of a zero. That happens to be harmless, but slightly inefficient. Consider the implementation of `newArray#` in [[GhcFile(rts/PrimOps.cmm)]]: {{{ stg_newArrayzh ( W_ n /* words */, gcptr init ) { W_ words, size; gcptr p, arr; again: MAYBE_GC(again); // the mark area contains one byte for each 2^MUT_ARR_PTRS_CARD_BITS words // in the array, making sure we round up, and then rounding up to a whole // number of words. size = n + mutArrPtrsCardWords(n); words = BYTES_TO_WDS(SIZEOF_StgMutArrPtrs) + size; ("ptr" arr) = ccall allocate(MyCapability() "ptr",words); TICK_ALLOC_PRIM(SIZEOF_StgMutArrPtrs, WDS(n), 0); SET_HDR(arr, stg_MUT_ARR_PTRS_DIRTY_info, CCCS); StgMutArrPtrs_ptrs(arr) = n; StgMutArrPtrs_size(arr) = size; // Initialise all elements of the the array with the value in R2 p = arr + SIZEOF_StgMutArrPtrs; for: if (p < arr + WDS(words)) { W_[p] = init; p = p + WDS(1); goto for; } // Initialise the mark bits with 0 for2: if (p < arr + WDS(size)) { W_[p] = 0; p = p + WDS(1); goto for2; } return (arr); } }}} The second for-loop never gets executed, as `size` < `words`. The first predicate should check `p < arr + SIZEOF_StgMutArrPtrs + WDS(n)` and the second should be `p < arr + WDS(words)`. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8867> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 4

Re: [GHC] #7633: Checkable "minimal complete definitions"
by GHC 13 Mar '14

13 Mar '14

#7633: Checkable "minimal complete definitions" -------------------------------------------------+------------------------- Reporter: shachaf | Owner: Type: feature request | twanvl Priority: normal | Status: Component: Compiler | closed Resolution: fixed | Milestone: 7.8.1 Operating System: Unknown/Multiple | Version: 7.6.1 Type of failure: None/Unknown | Keywords: Test Case: warnings/minimal/WarnMinimal | Architecture: Blocking: | Unknown/Multiple | Difficulty: | Unknown | Blocked By: | Related Tickets: #6028 -------------------------------------------------+------------------------- Comment (by Fuuzetsu): We've now pushed rendering of MINIMAL into Haddock. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/7633#comment:54> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

Re: [GHC] #7633: Checkable "minimal complete definitions"
by GHC 13 Mar '14

13 Mar '14

#7633: Checkable "minimal complete definitions" -------------------------------------------------+------------------------- Reporter: shachaf | Owner: Type: feature request | twanvl Priority: normal | Status: Component: Compiler | closed Resolution: fixed | Milestone: 7.8.1 Operating System: Unknown/Multiple | Version: 7.6.1 Type of failure: None/Unknown | Keywords: Test Case: warnings/minimal/WarnMinimal | Architecture: Blocking: | Unknown/Multiple | Difficulty: | Unknown | Blocked By: | Related Tickets: #6028 -------------------------------------------------+------------------------- Comment (by Lemming): Interested in an experience report? I added MINIMAL pragmas to numeric- prelude classes. I did several mistakes when transferring human description to MINIMAL pragma, mostly mixing up comma and bar. These mistakes were revealed by instances that gave wrong alarms. However one alarm was serious and spotted a missing method implementation in a cycle of default definitions. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/7633#comment:53> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

Re: [GHC] #3693: Show stack traces
by GHC 13 Mar '14

13 Mar '14

#3693: Show stack traces -------------------------------------+------------------------------------ Reporter: jpet | Owner: Tarrasch Type: feature request | Status: new Priority: normal | Milestone: 7.10.1 Component: Runtime System | Version: 6.10.4 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Unknown/Multiple Type of failure: None/Unknown | Difficulty: Unknown Test Case: | Blocked By: Blocking: | Related Tickets: -------------------------------------+------------------------------------ Comment (by scpmw): Okay, I have now submitted an (hopefully) improved version: https://github.com/scpmw/ghc/pull/6 The main new idea is that instead of `tickishScoped`+`tickishSoftScope` and `tickishIgnoreCheap` respectively we now have two main tickish properties: - Scoping ([https://github.com/scpmw/ghc/commit/0798888f829fe527b7c03f7d73b1d04746183b64 #diff-90615b0b9a679ebb599d2cb8b2c0dcdeR519 Source]): Determines what transformations are allowed with respect to covered code. The three levels are `NoScope` for don't-care (= HPC ticks), `SoftScope` for no-float-out and `CostCentreScope` for no-float-out plus no-float-in modulo lambdas. - Placement ([https://github.com/scpmw/ghc/commit/0798888f829fe527b7c03f7d73b1d04746183b64 #diff-90615b0b9a679ebb599d2cb8b2c0dcdeR648 Source]): It occurred to me that `mkTick` has a very similar problem with characterising where to create ticks / what to automatically push them through. So I did basically the same thing - the three levels here are `PlaceRuntime` which basically floats through just type applications and casts, `PlaceNonLam` which additionally floats through lambdas, and `PlaceCostCentre` which again implements all the CC-specific rules (such as eliminating ticks on HNFs). Note that the difference between `PlaceRuntime` and `PlaceNonLam` is essentially `tickishCounts`. However, it's actually easier this way, as it allows `mkTick` to do its work without having to care about `tickishCounts` at all ([https://github.com/scpmw/ghc/commit/0798888f829fe527b7c03f7d73b1d04746183b64 #diff-3ff04cec4ec4aff71838022111551fb8R232 Source]). Furthermore I tried to update all documentation and add more comments all around. What is the last verdict on a Wiki page? Sorry if I'm a bit reluctant about this, but I can't think of anything offhand that I would want to put on a Wiki instead of into a code comment. Some more examples, possibly? Btw: A non-paywall link to the paper is http://eprints.whiterose.ac.uk/76448/ -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/3693#comment:68> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

[GHC] #8884: Producing Slime For a Halloween Party
by GHC 13 Mar '14

13 Mar '14

#8884: Producing Slime For a Halloween Party --------------------------------------------+------------------------------ Reporter: ciagogou | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler (LLVM) | Version: 7.6.3 Keywords: Simply Green Coffee Bean | Operating System: Architecture: Unknown/Multiple | Unknown/Multiple Difficulty: Unknown | Type of failure: Blocked By: | None/Unknown Related Tickets: | Test Case: | Blocking: --------------------------------------------+------------------------------ Do you need to do a immunology proceed which passions as nicely as enhances the skillfulness of your kid virtually the study? If so, then correct here are both directive immunology tasks for little children that give not exclusive ameliorate their tendency, but also have them entertained and occupied. Generating goo faculty be amusing. It is a artist schoolhouse alchemy move. If you possess several knowledge some adding a lot author personalty to muck, condition it to your kid. Matter has numerous variations. Essentially, white cement and borax are the crucial components for producing gunk. Flubber is a singular of its palatable types. Stone spikes are yet added lanceolate and berth see externalise which entails evaporating a medicine of Epsom flavourer on construction medium. When this is settled, it results in crystals with vibrant glasses. New chemical substances these kinds of as seasoning, sweetening and borax can also be utilised. Simply Green Coffee Bean Baking soda volcano is truly simple to act. It does demand whatever origination grooming equal creating the strobilus of a crevice as the baking soda finding as to afflict from the voice. In consideration the hot tonic fox does not direct, then use all the substances that utilized to represent Mentos and fasting regime tonic to generate a crack expeditious. If you youngsters adore to connection you in the kitchen atlantic, then kind both pareve matter items equal dulcify crystals. This can be second intense and desires to be supervised as it involves burning and cooking. Or else, you can unify ice toiletry components unitedly and educate immature children the conception of freezing and melancholy. Instead, you can apprise kids nigh acidity and basicity by giving them a pH publisher and allowing them see few abode cleansing artifact. Erst again this is a supervised employ as it entails chemical compounds. We've noticed Soul Boozing water Sculpture (WWM) in watery pools for virtually 20 some period. Now we are outset to see it spas & sizzling tubs as nicely. WWM is a "naturally" ocurring flora that can inform up anyplace there is h2o or moisture. Consumers are line and asking about and mentioning a "moist paper equivalent" capital on the ascend area(s) of the spa take, filtrate pleats and remaining places. Occasionally, a thin "pinkish" coloring is seen alongside the spoilage. That is titled "flower slime." The two often go hand-in-hand. Unfortunately, by the dimension you license the WWM or knock goo in the spa alone, it nearly ofttimes signifies that the measure lines, jets, viscus components, and more others. are totally plagued. By the way, WWM & Ping matter is not serious - it fair appears Really inferior. How do you get rid of it? With lots or line! The WWM is a biofilm that builds up overtime in the trade lines & progressively spreads all the way finished the spa. Clients usually maintain that the spa has a "funky" sensation and they can't conserves a uppercase present of sanitizer (gas, bromine, or biguanide). The biofilm construct-up is Quite resilient versus any sort of shocking or higher ranges of halogens (element or element). The land billet is you require to knob it evenhandedly than hold it. http://trysimplygreencoffee.com/ -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8884> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

[GHC] #8882: Anatomy Muscles
by GHC 13 Mar '14

13 Mar '14

#8882: Anatomy Muscles -----------------------------------------+--------------------------------- Reporter: coustato | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Data Parallel Haskell | Version: 7.6.3 Keywords: Nitric Max Muscle | Operating System: Architecture: arm | Unknown/Multiple Difficulty: Difficult (2-5 days) | Type of failure: Runtime Blocked By: | crash Related Tickets: | Test Case: | Blocking: -----------------------------------------+--------------------------------- Morphology Muscles - Muscles Chart - Muscles Accumulation These 5 steps expose the things you dead Staleness Refrain if you essential to larghetto the aging touch, reprocess your upbeat, and attain your ideal body (Morphology Muscles - Muscles Interpret - Muscles Magnitude). Nitric Max Muscle What you impoverishment is a disperse of insensate liquid, a signature of Old Polish, and the artless emancipationist. Quantify good? Let's diving in! Interval 1: Bury Low-Fat Diets Support 2: Spot Running in Circles Support 3: Preclude Blaming Everything On How Old You Are Tread 4: Desist Degenerative Extraction Block 5: Impact Out Fewer (Yes, Less) Support 6: Anatomy Muscles - Muscles Chart - Muscles Accumulation Now You Can Unhurried The Old Affect To A Crawling, Quick Forge The Embody You've Always Welcome, Quality Alter It Sensing As If You're Aging 'Backwards' And Do It All In Fitting 90 Transactions A Period FACT: Our bodies all age, one day at a period. Withal: You can Inactive the old outgrowth physician and totally mold your body to the direction to where you sensing a decade junior than you are manus now in little than 90 days. This does not relate special creams, or whatsoever benevolent of 'miracle' FACT: Most people understand that both men and women Staleness work in order to grow affirm the timepiece. But did you experience that both men and women should essentially utilise out the comparable? Trusty, men leave use statesman metric, but the fright of women "getting bulky" is a MYTH and construe on. We'll substantiate it to you with pictures! FACT: You bang been lied to if you opine you human to rise large weights hours a day to countenance similar a complete stud, or that women status to terminate differently than men. We BOTH beggary LESS Clip in the gym, and we BOTH necessity the same fundamental prescript. Exclusive the status instrument change. FACT: You cannot gain this youth-enhancing System anywhere added. Becky and I hit restore control of it, and it's only initiate reactionary here, on this Anatomy Muscles - Muscles Chart - Muscles Massso ready readingÃ¢ I'm not asking you to vindicatory "buy a fact". I'm asking you to scan what Becky and I jazz to say in this laurels. It affects anyone over the age of especially if you are touch an age where you are mentation to yourself, "Vessel, I'm old it's downhill from Morphology Muscles - Muscles Chart - Muscles Collection." http://trynitricmaxmuscle.com/ -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8882> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

[GHC] #8864: Document heap allocation functions in StgCmmMonad/StgCmmLayout
by GHC 13 Mar '14

13 Mar '14

#8864: Document heap allocation functions in StgCmmMonad/StgCmmLayout ------------------------------------+------------------------------------- Reporter: tibbe | Owner: Type: feature request | Status: new Priority: normal | Milestone: Component: Documentation | Version: 7.6.3 Keywords: | Operating System: Unknown/Multiple Architecture: Unknown/Multiple | Type of failure: None/Unknown Difficulty: Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | ------------------------------------+------------------------------------- I'm having a hard time using the heap allocation functions in `StgCmmMonad` and `StgCmmLayout`, as they lack documentation. I'd be very grateful if someone could at least document: * `getHpRelOffset` * `setVirtHp` * `getVirtHp` To get an idea which questions I'm struggling with, I need to e.g. understand if the value returned by `getHpRelOffset` is affected by later calls to `setVirtHp`. This is probably obvious to some, but reading the code alone is not enough to get a good understanding how all the heap allocation code hangs together. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8864> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 9

Re: [GHC] #7633: Checkable "minimal complete definitions"
by GHC 13 Mar '14

13 Mar '14

#7633: Checkable "minimal complete definitions" -------------------------------------------------+------------------------- Reporter: shachaf | Owner: Type: feature request | twanvl Priority: normal | Status: Component: Compiler | closed Resolution: fixed | Milestone: 7.8.1 Operating System: Unknown/Multiple | Version: 7.6.1 Type of failure: None/Unknown | Keywords: Test Case: warnings/minimal/WarnMinimal | Architecture: Blocking: | Unknown/Multiple | Difficulty: | Unknown | Blocked By: | Related Tickets: #6028 -------------------------------------------------+------------------------- Comment (by haasn): Thanks, can't believe I missed that! I didn't think about looking inside the tcdSigs. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/7633#comment:52> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

Re: [GHC] #7633: Checkable "minimal complete definitions"
by GHC 13 Mar '14

13 Mar '14

#7633: Checkable "minimal complete definitions" -------------------------------------------------+------------------------- Reporter: shachaf | Owner: Type: feature request | twanvl Priority: normal | Status: Component: Compiler | closed Resolution: fixed | Milestone: 7.8.1 Operating System: Unknown/Multiple | Version: 7.6.1 Type of failure: None/Unknown | Keywords: Test Case: warnings/minimal/WarnMinimal | Architecture: Blocking: | Unknown/Multiple | Difficulty: | Unknown | Blocked By: | Related Tickets: #6028 -------------------------------------------------+------------------------- Comment (by simonpj): It's there already. The `tcdSigs` field of a `ClassDecl` can include a `MinimalSig`. What am I missing? Simon -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/7633#comment:51> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0