Re: [GHC] #1747: debugger: :trace is wasting time

2008-10-04 Thread GHC 
#1747: debugger: :trace is wasting time
--+-
 Reporter:  simonmar  |  Owner:  
 Type:  compile-time performance bug  | Status:  new 
 Priority:  normal|  Milestone:  6.12 branch 
Component:  GHCi  |Version:  6.6.1   
 Severity:  minor | Resolution:  
 Keywords:| Difficulty:  Unknown 
 Testcase:|   Architecture:  Unknown/Multiple
   Os:  Unknown/Multiple  |  
--+-
Changes (by igloo):

  * priority:  low = normal
  * milestone:  6.10.1 = 6.12 branch

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/1747#comment:7
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #1747: debugger: :trace is wasting time

2008-06-20 Thread GHC 
#1747: debugger: :trace is wasting time
--+-
 Reporter:  simonmar  |  Owner: 
 Type:  compile-time performance bug  | Status:  new
 Priority:  low   |  Milestone:  6.10.1 
Component:  GHCi  |Version:  6.6.1  
 Severity:  minor | Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  Unknown
   Os:  Unknown   |  
--+-
Changes (by igloo):

  * milestone:  6.8.3 = 6.10.1

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/1747#comment:4
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #1747: debugger: :trace is wasting time

2008-01-07 Thread GHC 
#1747: debugger: :trace is wasting time
--+-
 Reporter:  simonmar  |  Owner: 
 Type:  compile-time performance bug  | Status:  new
 Priority:  low   |  Milestone:  6.8.3  
Component:  GHCi  |Version:  6.6.1  
 Severity:  minor | Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  Unknown
   Os:  Unknown   |  
--+-
Changes (by simonmar):

  * type:  bug = compile-time performance bug

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/1747#comment:3
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #1747: debugger: :trace is wasting time

2007-11-13 Thread GHC 
#1747: debugger: :trace is wasting time
--+-
 Reporter:  simonmar  |  Owner: 
 Type:  bug   | Status:  new
 Priority:  low   |  Milestone:  6.8.3  
Component:  GHCi  |Version:  6.6.1  
 Severity:  minor | Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  Unknown
   Os:  Unknown   |  
--+-
Changes (by simonmar):

  * milestone:  6.8 branch = 6.8.3

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/1747#comment:2
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #1747: debugger: :trace is wasting time

2007-09-28 Thread GHC 
#1747: debugger: :trace is wasting time
-+--
Reporter:  simonmar  |Owner:
Type:  bug   |   Status:  new   
Priority:  low   |Milestone:  6.8 branch
   Component:  GHCi  |  Version:  6.6.1 
Severity:  minor |   Resolution:
Keywords:|   Difficulty:  Unknown   
  Os:  Unknown   | Testcase:
Architecture:  Unknown   |  
-+--
Old description:

 When using `:trace`, executing is constantly switching between the main
 GHCi thread and the execution thread.  The main GHCi thread is a bound
 thread, whereas the other thread is an unbound thread, so these context
 switches are real OS-thread switches, consequently `:trace` wastes a lot
 of time context-switching.

 Perhaps the main GHCi thread in an unbound thread, or else `:trace`
 should fork an unbound thread before starting execution.

New description:

 When using `:trace`, execution is constantly switching between the main
 GHCi thread and the execution thread.  The main GHCi thread is a bound
 thread, whereas the other thread is an unbound thread, so these context
 switches are real OS-thread switches, consequently `:trace` wastes a lot
 of time context-switching.

 Perhaps the main GHCi thread should be an unbound thread, or else `:trace`
 should fork an unbound thread before starting execution.

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/1747#comment:1
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

[GHC] #1747: debugger: :trace is wasting time

2007-09-28 Thread GHC 
#1747: debugger: :trace is wasting time
---+
  Reporter:  simonmar  |  Owner:
  Type:  bug   | Status:  new   
  Priority:  low   |  Milestone:  6.8 branch
 Component:  GHCi  |Version:  6.6.1 
  Severity:  minor |   Keywords:
Difficulty:  Unknown   | Os:  Unknown   
  Testcase:|   Architecture:  Unknown   
---+
 When using `:trace`, executing is constantly switching between the main
 GHCi thread and the execution thread.  The main GHCi thread is a bound
 thread, whereas the other thread is an unbound thread, so these context
 switches are real OS-thread switches, consequently `:trace` wastes a lot
 of time context-switching.

 Perhaps the main GHCi thread in an unbound thread, or else `:trace` should
 fork an unbound thread before starting execution.

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/1747
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs