[m5-dev] [PATCH] Config: Cause a fatal() when a parameter without a default value isn't set(FS #315)

2009-01-29 Thread Ali Saidi
# HG changeset patch # User Ali Saidi sa...@eecs.umich.edu # Date 1233270761 18000 # Node ID 5ca5f9050c0362cc54c386d19919c830d9e658f6 # Parent 130e1935985739d0727c51fd94c0d0b26a8b8ce7 Config: Cause a fatal() when a parameter without a default value isn't set(FS #315). diff --git

Re: [m5-dev] [PATCH] Config: Cause a fatal() when a parameter without a default value isn't set(FS #315)

2009-01-29 Thread Steve Reinhardt
Looks like the other error (right above the one you added) should be changed from a panic to a fatal as well. Steve On Thu, Jan 29, 2009 at 3:22 PM, Ali Saidi sa...@umich.edu wrote: This is a simple patch to fix FlySpray issue #315. We don't panic if a parameter without a default value isn't

Re: [m5-dev] [PATCH] Config: Cause a fatal() when a parameter without a default value isn't set(FS #315)

2009-01-29 Thread nathan binkert
This is a simple patch to fix FlySpray issue #315. We don't panic if a parameter without a default value isn't set which is a problem if the reason a default isn't set is that the user really needs to set one. I'm sending this mostly for Nate to say he is fine with doing it this way. Are

Re: [m5-dev] [PATCH] Config: Cause a fatal() when a parameter without a default value isn't set(FS #315)

2009-01-29 Thread Ali Saidi
On Jan 30, 2009, at 1:38 AM, nathan binkert wrote: This is a simple patch to fix FlySpray issue #315. We don't panic if a parameter without a default value isn't set which is a problem if the reason a default isn't set is that the user really needs to set one. I'm sending this mostly for