Re: [GHC] #1042: Floating point exception

[GHC]

#1042: Floating point exception
---+
  Reporter:  dons  |  Owner:  igloo   
  Type:  merge | Status:  closed  
  Priority:  normal|  Milestone:  6.6.1   
 Component:  Compiler  |Version:  6.6 
Resolution:  fixed |   Keywords:  
Difficulty:  Unknown   | Os:  Unknown/Multiple
  Testcase:|   Architecture:  x86 
   Failure:  None/Unknown  |  
---+
Changes (by jod):

  * failure:  => None/Unknown


Comment:

 * [http://www.javascr.com free text hosting]
  * [http://www.pharmacieenfrance.fr Acheter Generique France Sans
 Ordonnance, Achat Medicaments bon marche sur internet]
  * [http://www.farmaciaespanola.es Farmacia Española , Comprar Genericos
 En España Sin Receta , Compra Medicamentos Por Internet]
  * [http://med-assistant.info Medical Assistant - Your Assistant Online]
  * [http://med-assistant.info/FR/ L'Assistant Medical - Ton Assistant en
 ligne]

-- 
Ticket URL: 
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] #1042: Floating point exception

[GHC]

#1042: Floating point exception
--+-
 Reporter:  dons  |  Owner:  igloo  
 Type:  merge | Status:  closed 
 Priority:  normal|  Milestone:  6.6.1  
Component:  Compiler  |Version:  6.6
 Severity:  normal| Resolution:  fixed  
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  x86
   Os:  Unknown   |  
--+-
Changes (by igloo):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 Merged to the 6.6 branch.

-- 
Ticket URL: 
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] #1042: Floating point exception

[GHC]

#1042: Floating point exception
--+-
 Reporter:  dons  |  Owner:  igloo  
 Type:  merge | Status:  new
 Priority:  normal|  Milestone:  6.6.1  
Component:  Compiler  |Version:  6.6
 Severity:  normal| Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  x86
   Os:  Unknown   |  
--+-
Changes (by igloo):

  * type:  bug => merge

-- 
Ticket URL: 
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] #1042: Floating point exception

[GHC]

#1042: Floating point exception
--+-
 Reporter:  dons  |  Owner:  igloo  
 Type:  bug   | Status:  new
 Priority:  normal|  Milestone:  6.6.1  
Component:  Compiler  |Version:  6.6
 Severity:  normal| Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  x86
   Os:  Unknown   |  
--+-
Changes (by igloo):

  * owner:  => igloo

-- 
Ticket URL: 
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] #1042: Floating point exception

[GHC]

#1042: Floating point exception
--+-
 Reporter:  dons  |  Owner: 
 Type:  bug   | Status:  new
 Priority:  normal|  Milestone:  6.6.1  
Component:  Compiler  |Version:  6.6
 Severity:  normal| Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  x86
   Os:  Unknown   |  
--+-
Comment (by simonmar):

 Those are certainly reasonable points - I'm happy to raise an exception in
 this case.

-- 
Ticket URL: 
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] #1042: Floating point exception

[GHC]

#1042: Floating point exception
--+-
 Reporter:  dons  |  Owner: 
 Type:  bug   | Status:  new
 Priority:  normal|  Milestone:  6.6.1  
Component:  Compiler  |Version:  6.6
 Severity:  normal| Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  x86
   Os:  Unknown   |  
--+-
Comment (by igloo):

 minBound seems to be a better answer than 0 to me, but I would prefer an
 exception to both of them. That way div would always either succeed or
 raise an exception (div by zero or overflow).

 Also, unlike addition overflow (say), we need to check for this happening
 anyway, so there is no performance advantage to just letting it wrap by
 itself.

 Finally, I would expect that programmers realise that addition,
 multiplication etc might wrap, but I suspect none have considered that
 division might.


 Thanks
 Ian

-- 
Ticket URL: 
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] #1042: Floating point exception

[GHC]

#1042: Floating point exception
--+-
 Reporter:  dons  |  Owner: 
 Type:  bug   | Status:  new
 Priority:  normal|  Milestone:  6.6.1  
Component:  Compiler  |Version:  6.6
 Severity:  normal| Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  x86
   Os:  Unknown   |  
--+-
Comment (by simonmar):

 None of the arithmetic operations on `Int` check for overflow, they all
 wrap around modulo the size of the `Int` type, so it seems to me we should
 be consistent and yield 0 for this case.  Haskell 98 says that overflow is
 implementation-defined, so it's up to us what we do.

 Anyway, the place is `GHC.Real`, in the the `Integral` instance for `Int`.
 Also the various other integral types in `GHC.Int` need the same
 treatment.

-- 
Ticket URL: 
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] #1042: Floating point exception

[GHC]

#1042: Floating point exception
--+-
 Reporter:  dons  |  Owner: 
 Type:  bug   | Status:  new
 Priority:  normal|  Milestone:  6.6.1  
Component:  Compiler  |Version:  6.6
 Severity:  normal| Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  x86
   Os:  Unknown   |  
--+-
Changes (by igloo):

  * milestone:  => 6.6.1

Comment:

 I can't see anything in Haskell98 about it, but raising ArithException
 Overflow looks like the right thing to me. This is the only case we need
 to worry about, right? (for each of the signed types).


 Thanks
 Ian

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